From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
Artemy Kovalyov <artemyko@mellanox.com>,
Eli Cohen <eli@mellanox.com>,
Jack Morgenstein <jackm@dev.mellanox.co.il>,
linux-rdma@vger.kernel.org,
Michael Guralnik <michaelgur@mellanox.com>,
netdev@vger.kernel.org, Or Gerlitz <ogerlitz@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>
Subject: [PATCH rdma-next 0/9] MR cache fixes and refactoring
Date: Thu, 27 Feb 2020 14:33:51 +0200 [thread overview]
Message-ID: <20200227123400.97758-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@mellanox.com>
Hi,
This series fixes various corner cases in the mlx5_ib MR
cache implementation, see specific commit messages for more
information.
Thanks
Jason Gunthorpe (8):
RDMA/mlx5: Rename the tracking variables for the MR cache
RDMA/mlx5: Simplify how the MR cache bucket is located
RDMA/mlx5: Always remove MRs from the cache before destroying them
RDMA/mlx5: Fix MR cache size and limit debugfs
RDMA/mlx5: Lock access to ent->available_mrs/limit when doing
queue_work
RDMA/mlx5: Fix locking in MR cache work queue
RDMA/mlx5: Revise how the hysteresis scheme works for cache filling
RDMA/mlx5: Allow MRs to be created in the cache synchronously
Michael Guralnik (1):
RDMA/mlx5: Move asynchronous mkey creation to mlx5_ib
drivers/infiniband/hw/mlx5/mlx5_ib.h | 33 +-
drivers/infiniband/hw/mlx5/mr.c | 642 +++++++++++--------
drivers/infiniband/hw/mlx5/odp.c | 2 +-
drivers/net/ethernet/mellanox/mlx5/core/mr.c | 22 +-
include/linux/mlx5/driver.h | 6 -
5 files changed, 404 insertions(+), 301 deletions(-)
--
2.24.1
next reply other threads:[~2020-02-27 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 12:33 Leon Romanovsky [this message]
2020-02-27 12:33 ` [PATCH mlx5-next 1/9] RDMA/mlx5: Move asynchronous mkey creation to mlx5_ib Leon Romanovsky
2020-02-27 19:41 ` Saeed Mahameed
2020-02-27 20:00 ` Jason Gunthorpe
2020-02-27 20:42 ` Saeed Mahameed
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=20200227123400.97758-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=artemyko@mellanox.com \
--cc=dledford@redhat.com \
--cc=eli@mellanox.com \
--cc=jackm@dev.mellanox.co.il \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=michaelgur@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=yishaih@mellanox.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).