All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dean <seattleplus@gmail.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Calvin Owens <jcalvinowens@gmail.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [GSoC Project] Implementing NFS v4.2
Date: Fri, 13 Apr 2012 16:05:08 -0700	[thread overview]
Message-ID: <4F88B124.9030002@gmail.com> (raw)
In-Reply-To: <1333682276.4792.32.camel@lade.trondhjem.org>

>
>
>
> The efficient sparse file read and fadvise support might be nice too,
> but I'd like to see numbers for how they improve matters before I feel
> comfortable saying yea or nay to adding those specific features.

Instead of '...but I'd like to see...' I assume you meant, '...since I'd 
like to see...', as it would be hard to see how they improve matters 
without actually implementing them.

Although for sparse file reads, I think the low overhead design to avoid 
bloating every file upon read in NFSv4.2 makes it easy to see the 
benefit without any implementation.  For ioadvise, I think the benefit 
will be dependent upon support from the exported file system (or 
possibly nfs server).  So any prototype would have to be combined with 
appropriate support in the server file system or nfs server.

Dean

  parent reply	other threads:[~2012-04-13 23:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06  0:03 [GSoC Project] Implementing NFS v4.2 Calvin Owens
2012-04-06  3:17 ` Myklebust, Trond
2012-04-10  0:27   ` Calvin Owens
2012-04-10  0:34     ` David Quigley
2012-04-10 23:32       ` Calvin Owens
2012-04-12  6:15         ` Dave Quigley
2012-04-14  0:58           ` Calvin Owens
2012-04-13 23:05   ` Dean [this message]
2012-04-14  0:56     ` Calvin Owens

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=4F88B124.9030002@gmail.com \
    --to=seattleplus@gmail.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=jcalvinowens@gmail.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 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.