From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v5 00/14] NFS/RDMA server patches for v4.6
Date: Tue, 1 Mar 2016 17:00:52 -0500 [thread overview]
Message-ID: <20160301220052.GF23792@fieldses.org> (raw)
In-Reply-To: <20160301180337.2492.4255.stgit@klimt.1015granger.net>
On Tue, Mar 01, 2016 at 01:05:14PM -0500, Chuck Lever wrote:
> Hi Bruce-
>
> I think these are ready for linux-next.
OK, applying for 4.6, thanks.
I still wonder whether the code makes incorrect assumptions about how
the server xdr encoder uses the reply xdr_buf. That might only affect
clients which constructed rather strange compounds. And shouldn't be
made any worse by these patches.
--b.
>
> 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 v4:
> - Rebased on v4.5-rc6
> - Replace confusing comments about NFSv4.1 over RDMA support
>
>
> Changes since v3:
> - Rebased on v4.5-rc5
> - Completed fix for Write chunk XDR padding
> - On error, svc_rdma_sendto() should close connection
>
>
> 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 (14):
> nfsd: Update NFS server comments related to RDMA support
> svcrdma: Find client-provided write and reply chunks once per reply
> svcrdma: Do not write xdr_buf::tail in a Write chunk
> svcrdma: Do not send Write chunk XDR pad with inline content
> nfsd: Lower NFSv4.1 callback message size limit
> svcrdma: Close connection when a send error occurs
> 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 | 26 +-
> fs/nfsd/nfs4xdr.c | 2
> include/linux/sunrpc/auth.h | 7
> include/linux/sunrpc/rpc_rdma.h | 1
> include/linux/sunrpc/svc_rdma.h | 20 +
> net/sunrpc/auth_null.c | 4
> net/sunrpc/auth_unix.c | 6
> net/sunrpc/xprtrdma/svc_rdma_backchannel.c | 17 -
> net/sunrpc/xprtrdma/svc_rdma_marshal.c | 64 +++-
> net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 60 ++--
> net/sunrpc/xprtrdma/svc_rdma_sendto.c | 196 ++++++++----
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 445 +++++++++-------------------
> 12 files changed, 393 insertions(+), 455 deletions(-)
>
> --
> Chuck Lever
next prev parent reply other threads:[~2016-03-01 22:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 18:05 [PATCH v5 00/14] NFS/RDMA server patches for v4.6 Chuck Lever
2016-03-01 18:05 ` [PATCH v5 01/14] nfsd: Update NFS server comments related to RDMA support Chuck Lever
2016-03-01 18:05 ` [PATCH v5 02/14] svcrdma: Find client-provided write and reply chunks once per reply Chuck Lever
2016-03-01 18:05 ` [PATCH v5 03/14] svcrdma: Do not write xdr_buf::tail in a Write chunk Chuck Lever
2016-03-01 18:05 ` [PATCH v5 04/14] svcrdma: Do not send Write chunk XDR pad with inline content Chuck Lever
2016-03-01 18:06 ` [PATCH v5 05/14] nfsd: Lower NFSv4.1 callback message size limit Chuck Lever
2016-03-01 18:06 ` [PATCH v5 06/14] svcrdma: Close connection when a send error occurs Chuck Lever
2016-03-01 18:06 ` [PATCH v5 07/14] svcrdma: svc_rdma_post_recv() should close connection on error Chuck Lever
2016-03-01 18:06 ` [PATCH v5 08/14] rpcrdma: Add RPCRDMA_HDRLEN_ERR Chuck Lever
2016-03-01 18:06 ` [PATCH v5 09/14] svcrdma: Make RDMA_ERROR messages work Chuck Lever
2016-03-01 18:06 ` [PATCH v5 10/14] svcrdma: Use correct XID in error replies Chuck Lever
2016-03-01 18:06 ` [PATCH v5 11/14] svcrdma: Hook up the logic to return ERR_CHUNK Chuck Lever
2016-03-01 18:07 ` [PATCH v5 12/14] svcrdma: Remove close_out exit path Chuck Lever
2016-03-01 18:07 ` [PATCH v5 13/14] svcrdma: Use new CQ API for RPC-over-RDMA server receive CQs Chuck Lever
2016-03-01 18:07 ` [PATCH v5 14/14] svcrdma: Use new CQ API for RPC-over-RDMA server send CQs Chuck Lever
2016-03-01 22:00 ` J. Bruce Fields [this message]
2016-03-02 18:36 ` [PATCH v5 00/14] NFS/RDMA server patches for v4.6 Chuck Lever
2016-03-02 19:01 ` J. Bruce Fields
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=20160301220052.GF23792@fieldses.org \
--to=bfields@fieldses.org \
--cc=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).