All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 2/4] NFSD: Add READ_PLUS support for data segments
Date: Fri, 6 Feb 2015 03:54:56 -0800	[thread overview]
Message-ID: <20150206115456.GA28915@infradead.org> (raw)
In-Reply-To: <54D39DC2.9060808@Netapp.com>

On Thu, Feb 05, 2015 at 11:43:46AM -0500, Anna Schumaker wrote:
> > The problem is that the typical case of all data won't use splice
> > every with your patches as the 4.2 client will always send a READ_PLUS.
> > 
> > So we'll have to find a way to use it where it helps.  While we might be
> > able to add some hacks to only use splice for the first segment I guess
> > we just need to make the splice support generic enough in the long run.
> > 
> 
> I should be able to use splice if I detect that we're only returning a single DATA segment easily enough.

You could also elect to never return more than one data segment as a
start:

   In all situations, the
   server may choose to return fewer bytes than specified by the client.
   The client needs to check for this condition and handle the
   condition appropriately.

But doing any of these for a call that's really just an optimization
soudns odd.  I'd really like to see an evaluation of the READ_PLUS
impact on various workloads before offering it.

  parent reply	other threads:[~2015-02-06 11:55 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 20:42 [PATCH v2 0/4] NFSD: Add READ_PLUS support Anna.Schumaker
2015-01-28 20:42 ` [PATCH v2 1/4] NFSD: nfsd4_encode_read() should encode eof and maxcount Anna.Schumaker
2015-02-05 14:11   ` Christoph Hellwig
2015-02-05 16:04     ` Anna Schumaker
2015-01-28 20:42 ` [PATCH v2 2/4] NFSD: Add READ_PLUS support for data segments Anna.Schumaker
2015-02-05 14:13   ` Christoph Hellwig
2015-02-05 16:06     ` Anna Schumaker
2015-02-05 16:23       ` Christoph Hellwig
2015-02-05 16:43         ` Anna Schumaker
2015-02-05 16:48           ` J. Bruce Fields
2015-02-05 16:53             ` Anna Schumaker
2015-02-06 22:00             ` Anna Schumaker
2015-02-11 16:04             ` Anna Schumaker
2015-02-11 16:13               ` Trond Myklebust
2015-02-11 16:22                 ` J. Bruce Fields
2015-02-11 16:31                   ` Trond Myklebust
2015-02-11 16:42                     ` J. Bruce Fields
2015-02-12 12:32                       ` Christoph Hellwig
     [not found]                     ` <OF7B254253.7A276767-ON88257DE9.005F1E53-88257DE9.0060F512@us.ibm.com>
2015-02-11 17:47                       ` Trond Myklebust
2015-02-11 18:17                         ` Tom Haynes
2015-02-11 18:49                           ` Trond Myklebust
2015-02-11 19:01                             ` Anna Schumaker
2015-02-11 19:22                   ` Anna Schumaker
2015-02-12 19:59                     ` Anna Schumaker
2015-02-13 13:24                       ` Christoph Hellwig
2015-02-13 14:12                       ` J. Bruce Fields
2015-02-12 12:29                 ` Christoph Hellwig
2015-02-06 11:54           ` Christoph Hellwig [this message]
2015-02-06 16:08             ` J. Bruce Fields
2015-02-06 16:21               ` J. Bruce Fields
2015-02-06 16:46               ` Chuck Lever
2015-02-06 17:04                 ` Chuck Lever
2015-02-06 17:59                   ` J. Bruce Fields
2015-02-06 18:44                     ` Chuck Lever
2015-02-06 19:35                       ` J. Bruce Fields
2015-02-06 20:07                         ` Chuck Lever
2015-02-06 20:28                           ` J. Bruce Fields
2015-02-06 21:12                             ` Chuck Lever
2015-02-06 22:01                               ` J. Bruce Fields
2015-02-05 16:47       ` J. Bruce Fields
2015-01-28 20:42 ` [PATCH v2 3/4] NFSD: Add READ_PLUS support for hole segments Anna.Schumaker
2015-01-28 20:42 ` [PATCH v2 4/4] NFSD: Add support for encoding multiple segments Anna.Schumaker
2015-01-28 21:38 ` [PATCH v2 0/4] NFSD: Add READ_PLUS support Christoph Hellwig
2015-01-28 21:45   ` Anna Schumaker
2015-01-29 16:49     ` Anna Schumaker

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=20150206115456.GA28915@infradead.org \
    --to=hch@infradead.org \
    --cc=Anna.Schumaker@netapp.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.