From: Chuck Lever <chuck.lever@oracle.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v1 0/3] Handle NFSv4 operations in xdr_buf tail
Date: Fri, 18 Aug 2017 11:12:10 -0400 [thread overview]
Message-ID: <20170818150957.26571.12169.stgit@klimt.1015granger.net> (raw)
Hi Bruce-
A little light weekend reading. I got around to implementing
support in the NFSv4 WRITE decoder for dealing with trailing
operations that reside in the receiver buffer's tail iovec.
Let me know what you think of this solution.
---
Chuck Lever (3):
nfsd: Limit end of page list when decoding NFSv4 WRITE
nfsd: Incoming xdr_bufs may have content in tail buffer
svcrdma: Populate tail iovec when receiving
fs/nfsd/nfs4xdr.c | 26 ++++++++-
fs/nfsd/xdr4.h | 1
net/sunrpc/xprtrdma/svc_rdma_rw.c | 108 +++++--------------------------------
3 files changed, 38 insertions(+), 97 deletions(-)
--
Chuck Lever
next reply other threads:[~2017-08-18 15:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 15:12 Chuck Lever [this message]
2017-08-18 15:12 ` [PATCH v1 1/3] nfsd: Limit end of page list when decoding NFSv4 WRITE Chuck Lever
2017-08-21 21:13 ` J. Bruce Fields
2017-08-21 21:15 ` Chuck Lever
2017-08-21 21:21 ` J. Bruce Fields
2017-08-21 22:08 ` Chuck Lever
2017-08-22 21:45 ` J. Bruce Fields
2017-08-23 18:36 ` Chuck Lever
2017-08-24 1:18 ` J. Bruce Fields
2017-08-24 2:52 ` Weston Andros Adamson
2017-08-18 15:12 ` [PATCH v1 2/3] nfsd: Incoming xdr_bufs may have content in tail buffer Chuck Lever
2017-08-25 17:46 ` J. Bruce Fields
2017-08-18 15:12 ` [PATCH v1 3/3] svcrdma: Populate tail iovec when receiving 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=20170818150957.26571.12169.stgit@klimt.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@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).