From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Leon Romanovsky <leonro@mellanox.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Mark Zhang <markz@nvidia.com>
Subject: [PATCH rdma-next v3 0/5] Cleanup restrack code
Date: Tue, 22 Sep 2020 12:11:01 +0300 [thread overview]
Message-ID: <20200922091106.2152715-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Changelog:
v3:
* Removed the mlx4 SR-IOV patch in favour of more robust fix that not needed in
this series.
* Cut the eroginal series to already reviewed and standalone patches.
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:
* 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.
* https://lore.kernel.org/lkml/20200830101436.108487-1-leon@kernel.org
v0: https://lore.kernel.org/lkml/20200824104415.1090901-1-leon@kernel.org
----------------------------------------------------------------------------------
Leon Romanovsky (5):
RDMA/cma: Delete from restrack DB after successful destroy
RDMA/mlx5: Don't call to restrack recursively
RDMA/restrack: Count references to the verbs objects
RDMA/restrack: Simplify restrack tracking in kernel flows
RDMA/restrack: Improve readability in task name management
drivers/infiniband/core/cma.c | 140 +++++++++------
drivers/infiniband/core/core_priv.h | 13 +-
drivers/infiniband/core/counters.c | 15 +-
drivers/infiniband/core/cq.c | 9 +-
drivers/infiniband/core/restrack.c | 161 +++++++++---------
drivers/infiniband/core/restrack.h | 10 +-
drivers/infiniband/core/ucma.c | 7 +-
drivers/infiniband/core/uverbs_cmd.c | 27 ++-
drivers/infiniband/core/uverbs_std_types_cq.c | 8 +-
drivers/infiniband/core/verbs.c | 31 ++--
drivers/infiniband/hw/mlx5/gsi.c | 16 +-
include/rdma/rdma_cm.h | 47 ++---
include/rdma/restrack.h | 21 +--
13 files changed, 266 insertions(+), 239 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-22 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 9:11 Leon Romanovsky [this message]
2020-09-22 9:11 ` [PATCH rdma-next v3 1/5] RDMA/cma: Delete from restrack DB after successful destroy Leon Romanovsky
2020-09-22 9:11 ` [PATCH rdma-next v3 2/5] RDMA/mlx5: Don't call to restrack recursively Leon Romanovsky
2020-09-22 9:11 ` [PATCH rdma-next v3 3/5] RDMA/restrack: Count references to the verbs objects Leon Romanovsky
2020-09-22 9:11 ` [PATCH rdma-next v3 4/5] RDMA/restrack: Simplify restrack tracking in kernel flows Leon Romanovsky
2020-09-22 9:11 ` [PATCH rdma-next v3 5/5] RDMA/restrack: Improve readability in task name management Leon Romanovsky
2020-09-22 23:20 ` [PATCH rdma-next v3 0/5] Cleanup restrack code 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=20200922091106.2152715-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.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 \
/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;
as well as URLs for NNTP newsgroup(s).