From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Adit Ranadive <aditr@vmware.com>,
Ariel Elior <aelior@marvell.com>,
Faisal Latif <faisal.latif@intel.com>,
Lijun Ou <oulijun@huawei.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Maor Gottlieb <maorg@mellanox.com>,
Michal Kalderon <mkalderon@marvell.com>,
Shiraz Saleem <shiraz.saleem@intel.com>,
VMware PV-Drivers <pv-drivers@vmware.com>,
Weihang Li <liweihang@huawei.com>,
"Wei Hu(Xavier)" <huwei87@hisilicon.com>,
Yishai Hadas <yishaih@nvidia.com>
Subject: [PATCH rdma-next v1 00/10] Prepare drivers to move QP allocation to ib_core
Date: Sat, 26 Sep 2020 13:24:40 +0300 [thread overview]
Message-ID: <20200926102450.2966017-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Changelog:
v1:
* Rebased
* Fixed commit messages.
* Changed "fallthrough" to be "break".
v0: https://lore.kernel.org/lkml/20200910140046.1306341-1-leon@kernel.org
-------------------------------------------------------------------------
Hi,
This series mainly changes mlx4, mlx5, and mthca drivers to future
change of QP allocation scheme.
The rdmavt driver will be sent separately.
Thanks
Leon Romanovsky (10):
RDMA/mlx5: Embed GSI QP into general mlx5_ib QP
RDMA/mlx5: Reuse existing fields in parent QP storage object
RDMA/mlx5: Change GSI QP to have same creation flow like other QPs
RDMA/mlx5: Delete not needed GSI QP signal QP type
RDMA/mlx4: Embed GSI QP into general mlx4_ib QP
RDMA/mlx4: Prepare QP allocation to remove from the driver
RDMA/core: Align write and ioctl checks of QP types
RDMA/drivers: Remove udata check from special QP
RDMA/mthca: Combine special QP struct with mthca QP
RDMA/i40iw: Remove intermediate pointer that points to the same struct
drivers/infiniband/core/uverbs_cmd.c | 17 +-
drivers/infiniband/hw/hns/hns_roce_qp.c | 57 ++--
drivers/infiniband/hw/i40iw/i40iw_verbs.c | 9 +-
drivers/infiniband/hw/mlx4/mlx4_ib.h | 25 +-
drivers/infiniband/hw/mlx4/qp.c | 299 ++++++++-----------
drivers/infiniband/hw/mlx5/gsi.c | 138 +++------
drivers/infiniband/hw/mlx5/main.c | 6 +-
drivers/infiniband/hw/mlx5/mlx5_ib.h | 28 +-
drivers/infiniband/hw/mlx5/qp.c | 50 ++--
drivers/infiniband/hw/mthca/mthca_dev.h | 2 +-
drivers/infiniband/hw/mthca/mthca_provider.c | 17 +-
drivers/infiniband/hw/mthca/mthca_provider.h | 27 +-
drivers/infiniband/hw/mthca/mthca_qp.c | 75 +++--
drivers/infiniband/hw/qedr/verbs.c | 8 -
drivers/infiniband/hw/vmw_pvrdma/pvrdma_qp.c | 3 +-
15 files changed, 336 insertions(+), 425 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-26 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 10:24 Leon Romanovsky [this message]
2020-09-29 16:45 ` [PATCH rdma-next v1 00/10] Prepare drivers to move QP allocation to ib_core 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=20200926102450.2966017-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=aditr@vmware.com \
--cc=aelior@marvell.com \
--cc=dledford@redhat.com \
--cc=faisal.latif@intel.com \
--cc=huwei87@hisilicon.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=liweihang@huawei.com \
--cc=maorg@mellanox.com \
--cc=mkalderon@marvell.com \
--cc=oulijun@huawei.com \
--cc=pv-drivers@vmware.com \
--cc=shiraz.saleem@intel.com \
--cc=yishaih@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox