From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Ariel Levkovich <lariel@mellanox.com>,
Gal Pressman <galpress@amazon.com>,
Leon Romanovsky <leonro@mellanox.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Mark Zhang <markz@nvidia.com>, Yishai Hadas <yishaih@nvidia.com>
Subject: [PATCH rdma-next v5 0/3] Track memory allocation with restrack DB help (Part II)
Date: Tue, 17 Nov 2020 09:01:45 +0200 [thread overview]
Message-ID: <20201117070148.1974114-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Changelog:
v5:
* Reorder patches to postpone changes in rdma_restrack_add to be in next series.
v4: https://lore.kernel.org/linux-rdma/20201104144008.3808124-1-leon@kernel.org/
* Rebased on latest for-upstream, all that time the patches were in
our regression and didn't introduce any issues.
* Took first five patches that hadn't any comments
v3: https://lore.kernel.org/lkml/20200926101938.2964394-1-leon@kernel.org
* Rebased on already accepted patches.
* Added mlx4 special QPs to the list of not-tracked QPs (dropped previous mlx4 special QP patch).
* Separated to two patches change in return value of cma_listen_* routines.
* Changed commit messages and added Fixes as Jason requested.
v2: https://lore.kernel.org/linux-rdma/20200907122156.478360-1-leon@kernel.org/
* Added new patch to fix mlx4 failure on SR-IOV, it didn't have port set.
* Changed "RDMA/cma: Delete from restrack DB after successful destroy" patch.
v1: https://lore.kernel.org/lkml/20200830101436.108487-1-leon@kernel.org
* Fixed rebase error, deleted second assignment of qp_type.
* Rebased code on latests rdma-next, the changes in cma.c caused to change
in patch "RDMA/cma: Delete from restrack DB after successful destroy".
* Dropped patch of port assignment, it is already done as part of this
series.
* I didn't add @calller description, regular users should not use _named() funciton.
v0: https://lore.kernel.org/lkml/20200824104415.1090901-1-leon@kernel.org
----------------------------------------------------------------------------------
Leon Romanovsky (3):
RDMA/core: Track device memory MRs
RDMA/core: Allow drivers to disable restrack DB
RDMA/restrack: Support all QP types
drivers/infiniband/core/core_priv.h | 25 ++++++-------------
drivers/infiniband/core/counters.c | 2 +-
drivers/infiniband/core/restrack.c | 12 +++++++--
drivers/infiniband/core/uverbs_cmd.c | 4 +--
drivers/infiniband/core/uverbs_std_types_mr.c | 4 +++
drivers/infiniband/core/uverbs_std_types_qp.c | 4 +--
drivers/infiniband/core/verbs.c | 11 ++++----
drivers/infiniband/hw/mlx4/qp.c | 5 ++++
drivers/infiniband/hw/mlx5/qp.c | 2 +-
include/rdma/ib_verbs.h | 10 ++++++--
include/rdma/restrack.h | 24 ++++++++++++++++++
11 files changed, 70 insertions(+), 33 deletions(-)
--
2.28.0
next reply other threads:[~2020-11-17 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 7:01 Leon Romanovsky [this message]
2020-11-27 16:03 ` [PATCH rdma-next v5 0/3] Track memory allocation with restrack DB help (Part II) 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=20201117070148.1974114-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=galpress@amazon.com \
--cc=jgg@nvidia.com \
--cc=lariel@mellanox.com \
--cc=leonro@mellanox.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markz@nvidia.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