From: Chuck Lever <chuck.lever@oracle.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v1 0/2] NFS decoder clean-ups, redux
Date: Mon, 19 Mar 2018 14:56:43 -0400 [thread overview]
Message-ID: <20180319184647.10100.25736.stgit@klimt.1015granger.net> (raw)
Hi Bruce-
These two are pre-requisites for some transport level changes I'd
like to propose for v4.17.
I proposed these two for v4.16, you may recall. We had some
discussion about what changes you wanted but now I'm not sure I
recall your requests accurately.
I recall you felt OK with "NFSD: Clean up write argument XDR
decoders" but wanted some changes to "NFSD: Clean up symlink
argument XDR decoders".
Did you prefer that the symlink decoder should allocate a page
rather than pull it out of rq_pages[] ?
---
Chuck Lever (2):
NFSD: Clean up write argument XDR decoders
NFSD: Clean up symlink argument XDR decoders
fs/nfsd/nfs3proc.c | 18 ++++++-
fs/nfsd/nfs3xdr.c | 67 ++++++---------------------
fs/nfsd/nfs4proc.c | 37 +++++----------
fs/nfsd/nfs4xdr.c | 11 +++-
fs/nfsd/nfsproc.c | 23 ++++++---
fs/nfsd/nfsxdr.c | 63 +++++++++++++------------
fs/nfsd/xdr.h | 3 +
fs/nfsd/xdr3.h | 3 +
fs/nfsd/xdr4.h | 3 +
include/linux/sunrpc/svc.h | 4 ++
net/sunrpc/svc.c | 109 ++++++++++++++++++++++++++++++++++++++++++++
11 files changed, 217 insertions(+), 124 deletions(-)
--
Chuck Lever
next reply other threads:[~2018-03-19 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 18:56 Chuck Lever [this message]
2018-03-19 18:56 ` [PATCH v1 1/2] NFSD: Clean up write argument XDR decoders Chuck Lever
2018-03-23 21:32 ` J. Bruce Fields
2018-03-23 21:55 ` Chuck Lever
2018-03-23 22:37 ` Chuck Lever
2018-03-24 2:40 ` Bruce Fields
2018-03-24 16:00 ` Chuck Lever
2018-03-19 18:56 ` [PATCH v1 2/2] NFSD: Clean up symlink " 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=20180319184647.10100.25736.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.