Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: Trond.Myklebust@primarydata.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/3] NFS: Add READ_PLUS support
Date: Wed, 7 Jan 2015 13:24:12 -0500	[thread overview]
Message-ID: <20150107182412.GB7066@fieldses.org> (raw)
In-Reply-To: <1418855726-14262-1-git-send-email-Anna.Schumaker@Netapp.com>

On Wed, Dec 17, 2014 at 05:35:23PM -0500, Anna Schumaker wrote:
> 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.

So, what happens?  If that means we use just the first segment, and then
send another rpc for the rest, then this could lead to significant
performance regressions, couldn't it?

For example, if we synchronously read a 1-megabyte file consists of data
and holes alternating every 4k, then we've gone from waiting for a
single 1M read to waiting for 256 round trips.

I doubt that's a realistic example, but I don't know what is.  How do we
assure ourselves that this is an improvement?

Also, do we have good evidence that this does actually help
significantly when reading typical sparse files?  (Where I'm  not sure
how to define "typical"....)

--b.

> 
> 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
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2015-01-07 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 22:35 [PATCH 0/3] NFS: Add READ_PLUS support Anna Schumaker
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 [this message]

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=20150107182412.GB7066@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=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