From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neilb@ownmail.net>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Leon Romanovsky <leon@kernel.org>, Christoph Hellwig <hch@lst.de>
Cc: <linux-nfs@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v2 0/2] RDMA/rw: Fix MR pool exhaustion in bvec RDMA READ path
Date: Thu, 12 Mar 2026 09:40:06 -0400 [thread overview]
Message-ID: <20260312134008.7387-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
This series now carries the original fix with review comments
addressed, and a proposal for using contiguous pages for RDMA Read
sink buffers in svcrdma. IMO the fix patch should go into 7.0-rc,
and the RDMA Read behavior change can wait for the next merge
window.
Base commit: v7.0-rc3
---
Changes since v1:
- Clarify code comments
- Allocate contiguous pages for RDMA Read sink buffers
Chuck Lever (2):
RDMA/rw: Fix MR pool exhaustion in bvec RDMA READ path
svcrdma: Use contiguous pages for RDMA Read sink buffers
drivers/infiniband/core/rw.c | 16 ++-
net/sunrpc/xprtrdma/svc_rdma_rw.c | 220 ++++++++++++++++++++++++++++++
2 files changed, 229 insertions(+), 7 deletions(-)
--
2.52.0
next reply other threads:[~2026-03-12 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 13:40 Chuck Lever [this message]
2026-03-12 13:40 ` [PATCH v2 1/2] RDMA/rw: Fix MR pool exhaustion in bvec RDMA READ path Chuck Lever
2026-03-12 13:40 ` [PATCH v2 2/2] svcrdma: Use contiguous pages for RDMA Read sink buffers Chuck Lever
2026-03-13 8:51 ` kernel test robot
2026-03-13 12:34 ` Chuck Lever
2026-03-13 17:31 ` kernel test robot
2026-03-14 5:06 ` kernel test robot
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=20260312134008.7387-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=leon@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=neilb@ownmail.net \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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.