From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Mark Zhang <markz@mellanox.com>,
Christoph Hellwig <hch@infradead.org>
Subject: [PATCH rdma-next v1 0/7] Separate user/kernel QP creation logic
Date: Wed, 21 Jul 2021 12:07:03 +0300 [thread overview]
Message-ID: <cover.1626857976.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Changelog:
iv1:
* Fixed typo: incline -> inline/
* Dropped ib_create_qp_uverbs() wrapper in favour of direct call.
* Moved kernel-doc to the actual ib_create_qp() function that users will use.
v0: https://lore.kernel.org/lkml/cover.1626846795.git.leonro@nvidia.com
---------------------------------------------------------------------------
Hi,
The "QP allocation" series shows clearly how convoluted the create QP
flow and especially XRC_TGT flow, where it calls to kernel verb just
to pass some parameters as NULL to the user create QP verb.
This series is a small step to make clean XRC_TGT flow by providing
more clean user/kernel create QP verb separation.
It is based on the "QP allocation" series.
Thanks
Leon Romanovsky (7):
RDMA/mlx5: Delete not-available udata check
RDMA/core: Delete duplicated and unreachable code
RDMA/core: Remove protection from wrong in-kernel API usage
RDMA/core: Reorganize create QP low-level functions
RDMA/core: Configure selinux QP during creation
RDMA/core: Properly increment and decrement QP usecnts
RDMA/core: Create clean QP creations interface for uverbs
drivers/infiniband/core/core_priv.h | 59 +----
drivers/infiniband/core/uverbs_cmd.c | 31 +--
drivers/infiniband/core/uverbs_std_types_qp.c | 29 +--
drivers/infiniband/core/verbs.c | 208 +++++++++++-------
drivers/infiniband/hw/mlx5/qp.c | 3 -
include/rdma/ib_verbs.h | 16 +-
6 files changed, 157 insertions(+), 189 deletions(-)
--
2.31.1
next reply other threads:[~2021-07-21 9:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 9:07 Leon Romanovsky [this message]
2021-07-21 9:07 ` [PATCH rdma-next v1 1/7] RDMA/mlx5: Delete not-available udata check Leon Romanovsky
2021-07-21 9:07 ` [PATCH rdma-next v1 2/7] RDMA/core: Delete duplicated and unreachable code Leon Romanovsky
2021-07-21 9:07 ` [PATCH rdma-next v1 3/7] RDMA/core: Remove protection from wrong in-kernel API usage Leon Romanovsky
2021-07-21 9:07 ` [PATCH rdma-next v1 4/7] RDMA/core: Reorganize create QP low-level functions Leon Romanovsky
2021-07-21 9:07 ` [PATCH rdma-next v1 5/7] RDMA/core: Configure selinux QP during creation Leon Romanovsky
2021-07-21 9:07 ` [PATCH rdma-next v1 6/7] RDMA/core: Properly increment and decrement QP usecnts Leon Romanovsky
2021-07-21 9:07 ` [PATCH rdma-next v1 7/7] RDMA/core: Create clean QP creations interface for uverbs Leon Romanovsky
2021-08-03 18:10 ` [PATCH rdma-next v1 0/7] Separate user/kernel QP creation logic Leon Romanovsky
2021-08-03 18:13 ` Jason Gunthorpe
2021-08-03 18:17 ` Leon Romanovsky
2021-08-03 18:21 ` Leon Romanovsky
2021-08-03 18:26 ` Jason Gunthorpe
2021-08-03 23:33 ` Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1626857976.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=hch@infradead.org \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markz@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.