All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
	Gal Pressman <galpress@amazon.com>,
	Leon Romanovsky <leonro@mellanox.com>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	Maor Gottlieb <maorg@mellanox.com>, Mark Zhang <markz@nvidia.com>
Subject: [PATCH rdma-next 00/14] Track memory allocation with restrack DB help
Date: Mon, 24 Aug 2020 13:44:01 +0300	[thread overview]
Message-ID: <20200824104415.1090901-1-leon@kernel.org> (raw)

From: Leon Romanovsky <leonro@nvidia.com>

The resource tracker has built-in kref counter to synchronize object
release. It makes restrack perfect choice to be responsible for the
memory lifetime of any object in which restrack entry is embedded.

In order to make it, the restrack was changed to be mandatory and all
callers of rdma_restrack_add() started to rely on result returned from
that call. Being mandatory means that all objects specific to restrack
type must be tracked.

Before this series, the restrack and rdmatool were aid tools in debug
session of user space applications, this caused to some of the
functionality to be left behind, like support XRC QPs, device memory MRs
and QP0/QP1 in multi-port devices.

This series fixes all mentioned above without extending rdmatool at all.

Thanks

Leon Romanovsky (13):
  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
  RDMA/cma: Be strict with attaching to CMA device
  RDMA/core: Allow drivers to disable restrack DB
  RDMA/counter: Combine allocation and bind logic
  RDMA/restrack: Store all special QPs in restrack DB
  RDMA/restrack: Make restrack DB mandatory for IB objects
  RDMA/restrack: Support all QP types
  RDMA/core: Track device memory MRs
  RDMA/restrack: Drop valid restrack field as source of ambiguity

Maor Gottlieb (1):
  RDMA/verbs: Assign port number of special QPs

 drivers/infiniband/core/cma.c                 | 224 +++++++++++-------
 drivers/infiniband/core/core_priv.h           |  40 ++--
 drivers/infiniband/core/counters.c            | 178 +++++++-------
 drivers/infiniband/core/cq.c                  |  24 +-
 drivers/infiniband/core/rdma_core.c           |   3 +-
 drivers/infiniband/core/restrack.c            | 208 ++++++++--------
 drivers/infiniband/core/restrack.h            |  10 +-
 drivers/infiniband/core/uverbs_cmd.c          |  50 +++-
 drivers/infiniband/core/uverbs_std_types_cq.c |  12 +-
 drivers/infiniband/core/uverbs_std_types_mr.c |  10 +
 drivers/infiniband/core/uverbs_std_types_qp.c |   4 +-
 drivers/infiniband/core/verbs.c               |  94 ++++++--
 drivers/infiniband/hw/mlx5/gsi.c              |  16 +-
 drivers/infiniband/hw/mlx5/qp.c               |   2 +-
 include/rdma/ib_verbs.h                       |  10 +-
 include/rdma/restrack.h                       |  46 ++--
 16 files changed, 541 insertions(+), 390 deletions(-)

--
2.26.2


             reply	other threads:[~2020-08-24 10:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 10:44 Leon Romanovsky [this message]
2020-08-24 10:44 ` [PATCH rdma-next 01/14] RDMA/verbs: Assign port number of special QPs Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 02/14] RDMA/cma: Delete from restrack DB after successful destroy Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 03/14] RDMA/mlx5: Don't call to restrack recursively Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 04/14] RDMA/restrack: Count references to the verbs objects Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 05/14] RDMA/restrack: Simplify restrack tracking in kernel flows Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 06/14] RDMA/restrack: Improve readability in task name management Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 07/14] RDMA/cma: Be strict with attaching to CMA device Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 08/14] RDMA/core: Allow drivers to disable restrack DB Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 09/14] RDMA/counter: Combine allocation and bind logic Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 10/14] RDMA/restrack: Store all special QPs in restrack DB Leon Romanovsky
2020-08-26  8:04   ` Gal Pressman
2020-08-26  8:27     ` Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 11/14] RDMA/restrack: Make restrack DB mandatory for IB objects Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 12/14] RDMA/restrack: Support all QP types Leon Romanovsky
2020-08-26  8:03   ` Gal Pressman
2020-08-26  8:13     ` Leon Romanovsky
2020-08-26  8:17       ` Gal Pressman
2020-08-24 10:44 ` [PATCH rdma-next 13/14] RDMA/core: Track device memory MRs Leon Romanovsky
2020-08-24 10:44 ` [PATCH rdma-next 14/14] RDMA/restrack: Drop valid restrack field as source of ambiguity Leon Romanovsky

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=20200824104415.1090901-1-leon@kernel.org \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=galpress@amazon.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=maorg@mellanox.com \
    --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 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.