From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Patrisious Haddad <phaddad@nvidia.com>
Subject: [PATCH rdma-next 0/3] Allow parallel cleanup of HW objects
Date: Thu, 31 Oct 2024 13:22:50 +0200 [thread overview]
Message-ID: <cover.1730373303.git.leon@kernel.org> (raw)
This series from Patrisious adds a new device operation to allow the
driver to cleanup HW objects in parallel to the ufile cleanup. This is
useful for drivers that have HW objects that are not associated with a
kernel structures and doesn't have any dependencies on other objects.
In mlx5 case, we are using this new operation to cleanup DEVX QP
objects, which are independent from the rest verbs objects (like PD, CQ,
e.t.c).
Thanks
Patrisious Haddad (3):
RDMA/core: Add device ufile cleanup operation
RDMA/core: Move ib_uverbs_file struct to uverbs_types.h
RDMA/mlx5: Add implementation for ufile_hw_cleanup device operation
drivers/infiniband/core/device.c | 1 +
drivers/infiniband/core/rdma_core.c | 12 +++-
drivers/infiniband/core/uverbs.h | 31 ----------
drivers/infiniband/hw/mlx5/devx.c | 93 ++++++++++++++++++++++++++++-
drivers/infiniband/hw/mlx5/devx.h | 4 ++
drivers/infiniband/hw/mlx5/main.c | 1 +
include/rdma/ib_verbs.h | 6 ++
include/rdma/uverbs_types.h | 33 ++++++++++
8 files changed, 146 insertions(+), 35 deletions(-)
--
2.46.2
next reply other threads:[~2024-10-31 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 11:22 Leon Romanovsky [this message]
2024-10-31 11:22 ` [PATCH rdma-next 1/3] RDMA/core: Add device ufile cleanup operation Leon Romanovsky
2024-10-31 11:22 ` [PATCH rdma-next 2/3] RDMA/core: Move ib_uverbs_file struct to uverbs_types.h Leon Romanovsky
2024-10-31 11:22 ` [PATCH rdma-next 3/3] RDMA/mlx5: Add implementation for ufile_hw_cleanup device operation Leon Romanovsky
2024-11-04 8:46 ` [PATCH rdma-next 0/3] Allow parallel cleanup of HW objects 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=cover.1730373303.git.leon@kernel.org \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=phaddad@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).