Linux NFS development
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "bradley.kuszmaul@oracle.com" <bradley.kuszmaul@oracle.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: directory delegations
Date: Tue, 2 Apr 2019 20:28:22 -0400	[thread overview]
Message-ID: <20190403002822.GA7667@fieldses.org> (raw)
In-Reply-To: <58230e155813e866cb057e6543ab7e61f51fedf6.camel@hammerspace.com>

On Tue, Apr 02, 2019 at 09:51:42PM +0000, Trond Myklebust wrote:
> On Tue, 2019-04-02 at 15:41 -0400, J. Bruce Fields wrote:
> > On Tue, Apr 02, 2019 at 01:26:19PM -0400, Bradley C. Kuszmaul wrote:
> > > My simple model of metadata operations is to untar something like
> > > the linux sources.
> > > 
> > > Each file incurs a LOOKUP, CREATE, SETATTR, and WRITE, each of
> > > which
> > > is fairly high latency (even the WRITE ends up being done
> > > essentially synchronously because tar closes the file after its
> > > write(2) call.)
> > 
> > An ordinary file write delegation can help with some of that.
> > 
> > > I guess directory delegations might save the cost of LOOKUP.
> > > 
> > > Is there any hope for getting write delegations?
> > > 
> > > What other steps might be possible?
> > 
> > Trond, wasn't there a draft describing your idea that a server should
> > be
> > able to grant a write delegation on create and delay the sync?  I
> > can't
> > find it right now.
> 
> 
> Do you mean this one? 
> https://tools.ietf.org/html/draft-haynes-nfsv4-delstid-00

Maybe it's too subtle for me.  What's the part that allows delaying sync
on create?

--b.

  parent reply	other threads:[~2019-04-03  0:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 16:21 directory delegations Bradley C. Kuszmaul
2019-04-02 16:11 ` J. Bruce Fields
2019-04-02 17:26   ` Bradley C. Kuszmaul
2019-04-02 17:29     ` Bradley C. Kuszmaul
2019-04-02 19:41     ` J. Bruce Fields
2019-04-02 21:51       ` Trond Myklebust
2019-04-02 22:33         ` Trond Myklebust
2019-04-03  0:28         ` bfields [this message]
2019-04-03  2:02           ` Trond Myklebust
2019-04-03  2:07             ` bfields
2019-04-03 16:56               ` Bradley C. Kuszmaul
2019-04-04  1:05                 ` bfields
2019-04-04 15:09                   ` Jeff Layton
2019-04-04 15:22                     ` Chuck Lever
2019-04-04 15:36                       ` Jeff Layton
2019-04-04 20:03                       ` Bradley C. Kuszmaul
2019-04-04 20:41                         ` Bruce Fields
2019-04-04 20:45                           ` Bradley C. Kuszmaul
2019-04-04 15:37                     ` bfields
2019-04-04 15:44                       ` Jeff Layton

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=20190403002822.GA7667@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bradley.kuszmaul@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@hammerspace.com \
    /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