From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"bradley.kuszmaul@oracle.com" <bradley.kuszmaul@oracle.com>
Subject: Re: directory delegations
Date: Tue, 2 Apr 2019 22:07:50 -0400 [thread overview]
Message-ID: <20190403020750.GA8272@fieldses.org> (raw)
In-Reply-To: <ec8d33473da41b3bde45f5ef1b4a02b98a535ac5.camel@hammerspace.com>
On Wed, Apr 03, 2019 at 02:02:54AM +0000, Trond Myklebust wrote:
> The create itself needs to be sync, but the attribute delegations mean
> that the client, not the server, is authoritative for the timestamps.
> So the client now owns the atime and mtime, and just sets them as part
> of the (asynchronous) delegreturn some time after you are done writing.
>
> Were you perhaps thinking about this earlier proposal?
> https://tools.ietf.org/html/draft-myklebust-nfsv4-unstable-file-creation-01
That's it, thanks!
Bradley is concerned about performance of something like untar on a
backend filesystem with particularly high-latency metadata operations,
so something like your unstable file createion proposal (or actual write
delegations) seems like it should help.
--b.
next prev parent reply other threads:[~2019-04-03 2:07 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
2019-04-03 2:02 ` Trond Myklebust
2019-04-03 2:07 ` bfields [this message]
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=20190403020750.GA8272@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