From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: <Trond.Myklebust@primarydata.com>, <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/3] NFS: Add READ_PLUS support
Date: Wed, 17 Dec 2014 17:35:23 -0500 [thread overview]
Message-ID: <1418855726-14262-1-git-send-email-Anna.Schumaker@Netapp.com> (raw)
These patches add client support for the NFS v4.2 operation READ_PLUS. This
operation is triggered by doing any kind of read on a NFS v4.2 mounted
filesystem. `
The spec allows for the server to return multiple data and hole segments when
reading a file. Supporting this would requre a tedious amount of shifiting
to make sure data is aligned properly, so I'm skipping this feature until I
figure out a clean way of coding it.
These patches and the corresponding server changes are available in the
[read_plus] branch of
git://git.linux-nfs.org/projects/anna/linux-nfs.git
Questions? Comments? Thoughts?
Anna
Anna Schumaker (3):
NFS: Add basic support for READ_PLUS
SUNRPC: Add the ability to zero out data pages
NFS: Add support for reading NFS4_CONTENT_HOLE segments
fs/nfs/nfs42xdr.c | 159 +++++++++++++++++++++++++++++++++++++++++++++
fs/nfs/nfs4proc.c | 30 ++++++++-
fs/nfs/nfs4xdr.c | 1 +
include/linux/nfs4.h | 1 +
include/linux/nfs_fs_sb.h | 1 +
include/linux/nfs_xdr.h | 2 +-
include/linux/sunrpc/xdr.h | 1 +
net/sunrpc/xdr.c | 45 +++++++++++++
8 files changed, 237 insertions(+), 3 deletions(-)
--
2.1.3
next reply other threads:[~2014-12-17 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 22:35 Anna Schumaker [this message]
2014-12-17 22:35 ` [PATCH 1/3] NFS: Add basic support for READ_PLUS Anna Schumaker
2014-12-17 22:35 ` [PATCH 2/3] SUNRPC: Add the ability to zero out data pages Anna Schumaker
2014-12-17 22:35 ` [PATCH 3/3] NFS: Add support for reading NFS4_CONTENT_HOLE segments Anna Schumaker
2015-01-07 15:28 ` [PATCH 0/3] NFS: Add READ_PLUS support Anna Schumaker
2015-01-07 18:24 ` 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=1418855726-14262-1-git-send-email-Anna.Schumaker@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=Trond.Myklebust@primarydata.com \
--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