From: Michael Guralnik <michaelgur@nvidia.com>
To: <jgg@nvidia.com>, <leonro@nvidia.com>, <linux-rdma@vger.kernel.org>
Cc: <maorg@nvidia.com>, <aharonl@nvidia.com>,
Michael Guralnik <michaelgur@nvidia.com>
Subject: [PATCH v1 rdma-next 0/8] RDMA/mlx5: Switch MR cache to use RB-tree
Date: Mon, 7 Nov 2022 18:14:41 +0200 [thread overview]
Message-ID: <20221107161449.5611-1-michaelgur@nvidia.com> (raw)
This series moves the MR cache to use RB tree to store the entries of the
cache. By doing so, enabling more flexibility when managing the cache
entries.
The MR cache will now cache mkeys returned by the user even if they are
not from one of the predefined pools, by that allowing restarting
applications to reuse the their released mkey and improve restart times.
v0->v1:
- Fix rb tree search from memcmp to dedicated cmp function
- Rewording of some commit messages
Aharon Landau (8):
RDMA/mlx5: Don't keep umrable 'page_shift' in cache entries
RDMA/mlx5: Generalize mlx5_cache_cache_mr() to fit all cacheable mkeys
RDMA/mlx5: Remove explicit ODP cache entry
RDMA/mlx5: Allow rereg all the mkeys that can load pas with UMR
RDMA/mlx5: Introduce mlx5r_cache_rb_key
RDMA/mlx5: Change the cache structure to an RB-tree
RDMA/mlx5: Cache all user cacheable mkeys on dereg MR flow
RDMA/mlx5: Add work to remove temporary entries from the cache
drivers/infiniband/hw/mlx5/mlx5_ib.h | 42 +-
drivers/infiniband/hw/mlx5/mr.c | 574 ++++++++++++++++++++-------
drivers/infiniband/hw/mlx5/odp.c | 34 +-
include/linux/mlx5/driver.h | 1 -
4 files changed, 465 insertions(+), 186 deletions(-)
--
2.17.2
next reply other threads:[~2022-11-07 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 16:14 Michael Guralnik [this message]
2022-11-07 16:14 ` [PATCH v1 rdma-next 1/8] RDMA/mlx5: Don't keep umrable 'page_shift' in cache entries Michael Guralnik
2022-11-07 16:14 ` [PATCH v1 rdma-next 2/8] RDMA/mlx5: Generalize mlx5_cache_cache_mr() to fit all cacheable mkeys Michael Guralnik
2022-11-07 16:14 ` [PATCH v1 rdma-next 3/8] RDMA/mlx5: Remove explicit ODP cache entry Michael Guralnik
2022-11-07 16:14 ` [PATCH v1 rdma-next 4/8] RDMA/mlx5: Allow rereg all the mkeys that can load pas with UMR Michael Guralnik
2022-11-07 16:14 ` [PATCH v1 rdma-next 5/8] RDMA/mlx5: Introduce mlx5r_cache_rb_key Michael Guralnik
2022-11-07 16:14 ` [PATCH v1 rdma-next 6/8] RDMA/mlx5: Change the cache structure to an RB-tree Michael Guralnik
2022-11-07 16:14 ` [PATCH v1 rdma-next 7/8] RDMA/mlx5: Cache all user cacheable mkeys on dereg MR flow Michael Guralnik
2022-11-07 16:14 ` [PATCH v1 rdma-next 8/8] RDMA/mlx5: Add work to remove temporary entries from the cache Michael Guralnik
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=20221107161449.5611-1-michaelgur@nvidia.com \
--to=michaelgur@nvidia.com \
--cc=aharonl@nvidia.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@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).