From: Chuck Lever <chuck.lever@oracle.com>
To: bfields@fieldses.org
Cc: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH RFC2 0/3] Follow-up discussion of bug 198053
Date: Fri, 31 Jan 2020 15:41:39 -0500 [thread overview]
Message-ID: <20200131203727.31409.63652.stgit@bazille.1015granger.net> (raw)
Hi Bruce-
These are a proof-of-concept, not for merge.
This set of patches addresses the NFS/RDMA bug reported here:
https://bugzilla.kernel.org/show_bug.cgi?id=198053
This approach does not cause any regression of support for NFSv4
COMPOUNDs with multiple READ operations over TCP. It is also far
less invasive than my first try.
Thoughts, opinions?
---
Chuck Lever (3):
nfsd: Fix NFSv4 READ on RDMA when using readv
SUNRPC: Track current encode position in struct xdr_stream
NFSD: Enable nfsd4_encode_readv() for NFS/RDMA
fs/nfsd/nfs4proc.c | 1 +
fs/nfsd/nfs4xdr.c | 16 +++++++---------
include/linux/sunrpc/svc.h | 3 +++
include/linux/sunrpc/svc_rdma.h | 6 +++++-
include/linux/sunrpc/svc_xprt.h | 2 ++
include/linux/sunrpc/xdr.h | 1 +
net/sunrpc/svc.c | 14 ++++++++++++++
net/sunrpc/svcsock.c | 7 +++++++
net/sunrpc/xdr.c | 2 ++
net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 1 +
net/sunrpc/xprtrdma/svc_rdma_rw.c | 29 +++++++++++++++++++----------
net/sunrpc/xprtrdma/svc_rdma_sendto.c | 26 +++++++++++++++++++++++++-
net/sunrpc/xprtrdma/svc_rdma_transport.c | 1 +
13 files changed, 88 insertions(+), 21 deletions(-)
--
Chuck Lever
next reply other threads:[~2020-01-31 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 20:41 Chuck Lever [this message]
2020-01-31 20:41 ` [PATCH RFC2 1/3] nfsd: Fix NFSv4 READ on RDMA when using readv Chuck Lever
2020-01-31 20:41 ` [PATCH RFC2 2/3] SUNRPC: Track current encode position in struct xdr_stream Chuck Lever
2020-01-31 21:19 ` Trond Myklebust
2020-01-31 20:41 ` [PATCH RFC2 3/3] NFSD: Enable nfsd4_encode_readv() for NFS/RDMA 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=20200131203727.31409.63652.stgit@bazille.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=bfields@fieldses.org \
--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).