From: Jeff Layton <jlayton@kernel.org>
To: linux-nfs <linux-nfs@vger.kernel.org>
Cc: Rick Macklem <rick.macklem@gmail.com>
Subject: when should the client request a directory delegation?
Date: Wed, 07 Feb 2024 08:34:32 -0500 [thread overview]
Message-ID: <57b9f5e0c3ec7bc09044b016a3822d0700760c55.camel@kernel.org> (raw)
I've started work on a patchset to add support for directory delegations
to the Linux kernel client and server. It's still too rough to post at
this point, and for now, I'm just cobbling in a ioctl to drive it.
As I started working on some of the client bits, however, I realized
that I don't really have a clear picture as to when the client should
request a delegation on a directory. It seems like there are a lot of
things we could do:
One idea: request one on an initial directory readdir. So maybe when the
offset is 0 and we don't have a dir delegation already, do:
PUTFH:GET_DIR_DELEGATION:READDIR
Or, maybe just do it on any readdir when we haven't requested one in a
little while?
We could also do one on every lookup, when we expect that the result
will be a directory. I'm not sure if LOOKUP_DIRECTORY would be a
sufficient indicator or if we'd need the vfs to indicate that with a new
flag.
Would we also want to request one after a mkdir?
PUTFH:CREATE:GET_DIR_DELEGATION:GETFH:GET_DIR_DELEGATION:...
Assuming we can get this all working, what should drive the client to
issues GET_DIR_DELEGATION ops?
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2024-02-07 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 13:34 Jeff Layton [this message]
2024-02-07 14:21 ` when should the client request a directory delegation? Trond Myklebust
2024-02-07 14:56 ` Jeff Layton
2024-02-07 15:02 ` Trond Myklebust
2024-02-07 15:40 ` Jeff Layton
2024-02-07 14:56 ` Trond Myklebust
2024-02-07 15:18 ` 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=57b9f5e0c3ec7bc09044b016a3822d0700760c55.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rick.macklem@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;
as well as URLs for NNTP newsgroup(s).