From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v1 0/4] NFS/RDMA client for v4.21 (part 1)
Date: Mon, 19 Nov 2018 10:45:45 -0500 [thread overview]
Message-ID: <20181119153707.10832.42881.stgit@manet.1015granger.net> (raw)
Hi-
These four patches changes details of how the Linux RPC-over-RDMA
client implementation uses RDMA, thus I'd like some scrutiny by the
good people on linux-rdma.
I've got a dozen or so additional patches for v4.21 dealing with the
higher layers which I will post next week. I will aim those at
linux-nfs.
---
Chuck Lever (4):
xprtrdma: Remove support for FMR memory registration
xprtrdma: mrs_create off-by-one
xprtrdma: Reduce max_frwr_depth
xprtrdma: Plant XID in on-the-wire RDMA offset (FRWR)
net/sunrpc/xprtrdma/Makefile | 3
net/sunrpc/xprtrdma/fmr_ops.c | 337 ---------------------------------------
net/sunrpc/xprtrdma/frwr_ops.c | 20 ++
net/sunrpc/xprtrdma/rpc_rdma.c | 6 -
net/sunrpc/xprtrdma/verbs.c | 6 -
net/sunrpc/xprtrdma/xprt_rdma.h | 2
6 files changed, 19 insertions(+), 355 deletions(-)
delete mode 100644 net/sunrpc/xprtrdma/fmr_ops.c
--
Chuck Lever
next reply other threads:[~2018-11-19 15:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 15:45 Chuck Lever [this message]
2018-11-19 15:45 ` [PATCH v1 1/4] xprtrdma: Remove support for FMR memory registration Chuck Lever
2018-11-19 16:16 ` Bart Van Assche
2018-11-19 19:09 ` Leon Romanovsky
2018-11-19 20:52 ` Bart Van Assche
2018-11-20 5:37 ` Leon Romanovsky
2018-11-19 22:41 ` Jason Gunthorpe
2018-11-19 22:56 ` Chuck Lever
2018-11-19 23:10 ` Jason Gunthorpe
2018-11-20 15:22 ` Dennis Dalessandro
2018-11-19 15:45 ` [PATCH v1 2/4] xprtrdma: mrs_create off-by-one Chuck Lever
2018-11-19 15:46 ` [PATCH v1 3/4] xprtrdma: Reduce max_frwr_depth Chuck Lever
2018-11-19 15:46 ` [PATCH v1 4/4] xprtrdma: Plant XID in on-the-wire RDMA offset (FRWR) Chuck Lever
2018-11-19 17:47 ` Olga Kornievskaia
2018-11-19 17:58 ` Chuck Lever
2018-11-19 18:08 ` Olga Kornievskaia
2018-11-19 18:18 ` Chuck Lever
2018-11-19 18:47 ` Olga Kornievskaia
2018-11-19 18:58 ` Chuck Lever
2018-11-19 21:22 ` Olga Kornievskaia
2018-11-19 21:32 ` Chuck Lever
2018-11-19 21:42 ` Mora, Jorge
2018-11-19 22:46 ` Jason Gunthorpe
2018-11-20 2:45 ` Tom Talpey
2018-11-20 3:09 ` Jason Gunthorpe
2018-11-20 3:25 ` Tom Talpey
2018-11-20 3:32 ` Jason Gunthorpe
2018-11-20 3:38 ` Tom Talpey
2018-11-20 18:02 ` Anna Schumaker
2018-11-20 18:07 ` Chuck Lever
[not found] ` <94ff7ec712e086bfdd9c217a5f97c293a07151b9.camel@gmail.com>
2018-11-20 21:31 ` Chuck Lever
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=20181119153707.10832.42881.stgit@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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