From: bfields@fieldses.org (J. Bruce Fields)
To: "Bradley C. Kuszmaul" <bradley.kuszmaul@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: directory delegations
Date: Tue, 2 Apr 2019 12:11:16 -0400 [thread overview]
Message-ID: <20190402161116.GA2828@fieldses.org> (raw)
In-Reply-To: <2065755c-f888-9c62-f6e5-f143d42c51ee@oracle.com>
On Mon, Apr 01, 2019 at 12:21:49PM -0400, Bradley C. Kuszmaul wrote:
> Hi, I'm the architect for Oracle's File Storage Service. FSS is
> basically a big scalable NFS server that runs in Oracle's cloud.
>
> Our metadata operations have higher latency than a vanilla NFS
> server (e.g., a Linux NFS server serving a XFS stored on a block
> device), and we suspect that directory delegations would make a big
> performance improvement.
>
> I understand, however, that essentially no one implements directory
> delegations.
>
> Can anyone fill me in on the current thinking of the future of
> support for directory delegations in the Linux NFS client?
Maybe somebody else will speak up, but I don't know of any effort to
implement directory delegations.
What metadata operations specifically are you worried about? The
directory delegations that are specified in RFC 5661 are read-only.
Which might explain some of the lack of interest.
But there may be other steps that we could take to improve matters.
--b.
next prev parent reply other threads:[~2019-04-02 16:11 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 [this message]
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
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=20190402161116.GA2828@fieldses.org \
--to=bfields@fieldses.org \
--cc=bradley.kuszmaul@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox