From: Chuck Lever <chuck.lever@oracle.com>
To: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH v3 00/10] NFS/RDMA server patches for v4.6
Date: Thu, 18 Feb 2016 12:43:43 -0500 [thread overview]
Message-ID: <20160218173840.12825.26769.stgit@klimt.1015granger.net> (raw)
Two major changes: Finish server-side support for RDMA_ERROR type
messages, and convert the server's completion handlers to the new
core CQ API.
Also available in the "nfsd-rdma-for-4.6" topic branch of this git
repo:
git://git.linux-nfs.org/projects/cel/cel-2.6.git
Or for browsing:
http://git.linux-nfs.org/?p=cel/cel-2.6.git;a=log;h=refs/heads/nfsd-rdma-for-4.6
Changes since v2:
- Rebased on v4.5-rc4
- checkpatch.pl passes
- Fix iWARP RDMA Read path regression
- Reduce NFSv4.1 CB message size maximum in CREATE_SESSION
- Another pass at fixing Write chunk XDR padding
- Various clean ups
Changes since v1:
- Rebased on v4.5-rc3
- Patch 02/10 (pre-allocate frmrs) dropped
- Patch 04/10 replaced with more surgical patch
- Refined reporting of flushed completions
- Function names of completion methods changed to match client's
new completion function naming convention
---
Chuck Lever (10):
svcrdma: Do not write xdr_buf::tail in a Write chunk
nfsd: Lower NFSv4.1 callback message size limit
svcrdma: svc_rdma_post_recv() should close connection on error
rpcrdma: Add RPCRDMA_HDRLEN_ERR
svcrdma: Make RDMA_ERROR messages work
svcrdma: Use correct XID in error replies
svcrdma: Hook up the logic to return ERR_CHUNK
svcrdma: Remove close_out exit path
svcrdma: Use new CQ API for RPC-over-RDMA server receive CQs
svcrdma: Use new CQ API for RPC-over-RDMA server send CQs
fs/nfsd/nfs4state.c | 24 +-
include/linux/sunrpc/auth.h | 7
include/linux/sunrpc/rpc_rdma.h | 1
include/linux/sunrpc/svc_rdma.h | 18 +
net/sunrpc/auth_null.c | 4
net/sunrpc/auth_unix.c | 6
net/sunrpc/xprtrdma/svc_rdma_backchannel.c | 15 -
net/sunrpc/xprtrdma/svc_rdma_marshal.c | 64 +++-
net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 60 ++--
net/sunrpc/xprtrdma/svc_rdma_sendto.c | 88 +++++-
net/sunrpc/xprtrdma/svc_rdma_transport.c | 445 +++++++++-------------------
11 files changed, 333 insertions(+), 399 deletions(-)
--
Chuck Lever
next reply other threads:[~2016-02-18 17:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 17:43 Chuck Lever [this message]
2016-02-18 17:43 ` [PATCH v3 01/10] svcrdma: Do not write xdr_buf::tail in a Write chunk Chuck Lever
2016-02-22 18:32 ` J. Bruce Fields
2016-02-22 18:35 ` Chuck Lever
2016-02-22 18:39 ` Chuck Lever
2016-02-18 17:44 ` [PATCH v3 02/10] nfsd: Lower NFSv4.1 callback message size limit Chuck Lever
2016-02-18 17:53 ` Chuck Lever
2016-02-18 17:44 ` [PATCH v3 03/10] svcrdma: svc_rdma_post_recv() should close connection on error Chuck Lever
2016-02-18 17:44 ` [PATCH v3 04/10] rpcrdma: Add RPCRDMA_HDRLEN_ERR Chuck Lever
2016-02-18 17:44 ` [PATCH v3 05/10] svcrdma: Make RDMA_ERROR messages work Chuck Lever
2016-02-18 17:44 ` [PATCH v3 06/10] svcrdma: Use correct XID in error replies Chuck Lever
2016-02-18 17:44 ` [PATCH v3 07/10] svcrdma: Hook up the logic to return ERR_CHUNK Chuck Lever
2016-02-18 17:44 ` [PATCH v3 08/10] svcrdma: Remove close_out exit path Chuck Lever
2016-02-18 17:44 ` [PATCH v3 09/10] svcrdma: Use new CQ API for RPC-over-RDMA server receive CQs Chuck Lever
2016-02-18 17:45 ` [PATCH v3 10/10] svcrdma: Use new CQ API for RPC-over-RDMA server send CQs 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=20160218173840.12825.26769.stgit@klimt.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;
as well as URLs for NNTP newsgroup(s).