From: Michael Guralnik <michaelgur@nvidia.com>
To: <jgg@nvidia.com>
Cc: <leonro@nvidia.com>, <maorg@nvidia.com>,
<linux-kernel@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<netdev@vger.kernel.org>, <saeedm@nvidia.com>,
Michael Guralnik <michaelgur@nvidia.com>
Subject: [PATCH rdma-next v1 0/5] MR cache cleanup
Date: Tue, 26 Jul 2022 10:19:06 +0300 [thread overview]
Message-ID: <20220726071911.122765-1-michaelgur@nvidia.com> (raw)
Hi,
In this series, Aharon continues to clean mlx5 MR cache logic.
Thanks
v1: Change push_mkey to eliminate locking on mail flow
v0: http://lore.kernel.org/all/cover.1654601897.git.leonro@nvidia.com/
Aharon Landau (5):
RDMA/mlx5: Replace ent->lock with xa_lock
RDMA/mlx5: Replace cache list with Xarray
RDMA/mlx5: Store the number of in_use cache mkeys instead of total_mrs
RDMA/mlx5: Store in the cache mkeys instead of mrs
RDMA/mlx5: Rename the mkey cache variables and functions
drivers/infiniband/hw/mlx5/main.c | 4 +-
drivers/infiniband/hw/mlx5/mlx5_ib.h | 61 ++--
drivers/infiniband/hw/mlx5/mr.c | 514 +++++++++++++++------------
drivers/infiniband/hw/mlx5/odp.c | 2 +-
include/linux/mlx5/driver.h | 6 +-
5 files changed, 307 insertions(+), 280 deletions(-)
--
2.17.2
next reply other threads:[~2022-07-26 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 7:19 Michael Guralnik [this message]
2022-07-26 7:19 ` [PATCH rdma-next v1 1/5] RDMA/mlx5: Replace ent->lock with xa_lock Michael Guralnik
2022-07-26 7:19 ` [PATCH rdma-next v1 2/5] RDMA/mlx5: Replace cache list with Xarray Michael Guralnik
2022-07-26 7:19 ` [PATCH rdma-next v1 3/5] RDMA/mlx5: Store the number of in_use cache mkeys instead of total_mrs Michael Guralnik
2022-07-26 7:19 ` [PATCH rdma-next v1 4/5] RDMA/mlx5: Store in the cache mkeys instead of mrs Michael Guralnik
2022-07-26 7:19 ` [PATCH rdma-next v1 5/5] RDMA/mlx5: Rename the mkey cache variables and functions Michael Guralnik
2022-07-27 18:17 ` [PATCH rdma-next v1 0/5] MR cache cleanup 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=20220726071911.122765-1-michaelgur@nvidia.com \
--to=michaelgur@nvidia.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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