From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Bradley C. Kuszmaul" <bradley.kuszmaul@oracle.com>
Cc: linux-nfs@vger.kernel.org, Trond Myklebust <trondmy@gmail.com>
Subject: Re: directory delegations
Date: Tue, 2 Apr 2019 15:41:48 -0400 [thread overview]
Message-ID: <20190402194148.GA5269@fieldses.org> (raw)
In-Reply-To: <2f1f6582-3672-1361-4392-80cb1e62e19c@oracle.com>
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.
--b.
next prev parent reply other threads:[~2019-04-02 19:41 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 [this message]
2019-04-02 21:51 ` Trond Myklebust
2019-04-02 22:33 ` Trond Myklebust
2019-04-03 0:28 ` bfields
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=20190402194148.GA5269@fieldses.org \
--to=bfields@fieldses.org \
--cc=bradley.kuszmaul@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@gmail.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