From: Benjamin Coddington <bcodding@redhat.com>
To: trond.myklebust@hammerspace.com, anna@kernel.org
Cc: linux-nfs@vger.kernel.org, jlayton@kernel.org
Subject: Re: [PATCH v2] NFSv4: Always ask for type with READDIR
Date: Thu, 07 Sep 2023 08:43:40 -0400 [thread overview]
Message-ID: <202D34A7-61AC-44DA-B2C1-CCE109EC2A76@redhat.com> (raw)
In-Reply-To: <82d1908e4f835a2f16a509a11b62b9d93ccb6cdf.1693424491.git.bcodding@redhat.com>
Hello Trond and Anna - two questions:
Any chance of this going this cycle upon its merits of simplicity outweighing the lateness?
If no - can we expect it on 6.7, or should I continue to look for another approach that doesn't potentially penalize some servers?
Ben
On 30 Aug 2023, at 15:42, Benjamin Coddington wrote:
> Again we have claimed regressions for walking a directory tree, this time
> with the "find" utility which always tries to optimize away asking for any
> attributes until it has a complete list of entries. This behavior makes
> the readdir plus heuristic do the wrong thing, which causes a storm of
> GETATTRs to determine each entry's type in order to continue the walk.
>
> For v4 add the type attribute to each READDIR request to include it no
> matter the heuristic. This allows a simple `find` command to proceed
> quickly through a directory tree.
>
> Suggested-by: Jeff Layton <jlayton@kernel.org>
> Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
>
> --
> On v2: Don't add the type attribute twice
> ---
> fs/nfs/nfs4xdr.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/nfs4xdr.c b/fs/nfs/nfs4xdr.c
> index deec76cf5afe..7200d6f7cd7b 100644
> --- a/fs/nfs/nfs4xdr.c
> +++ b/fs/nfs/nfs4xdr.c
> @@ -1602,7 +1602,7 @@ static void encode_read(struct xdr_stream *xdr, const struct nfs_pgio_args *args
> static void encode_readdir(struct xdr_stream *xdr, const struct nfs4_readdir_arg *readdir, struct rpc_rqst *req, struct compound_hdr *hdr)
> {
> uint32_t attrs[3] = {
> - FATTR4_WORD0_RDATTR_ERROR,
> + FATTR4_WORD0_TYPE|FATTR4_WORD0_RDATTR_ERROR,
> FATTR4_WORD1_MOUNTED_ON_FILEID,
> };
> uint32_t dircount = readdir->count;
> @@ -1612,7 +1612,7 @@ static void encode_readdir(struct xdr_stream *xdr, const struct nfs4_readdir_arg
> unsigned int i;
>
> if (readdir->plus) {
> - attrs[0] |= FATTR4_WORD0_TYPE|FATTR4_WORD0_CHANGE|FATTR4_WORD0_SIZE|
> + attrs[0] |= FATTR4_WORD0_CHANGE|FATTR4_WORD0_SIZE|
> FATTR4_WORD0_FSID|FATTR4_WORD0_FILEHANDLE|FATTR4_WORD0_FILEID;
> attrs[1] |= FATTR4_WORD1_MODE|FATTR4_WORD1_NUMLINKS|FATTR4_WORD1_OWNER|
> FATTR4_WORD1_OWNER_GROUP|FATTR4_WORD1_RAWDEV|
> --
> 2.
next prev parent reply other threads:[~2023-09-07 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 19:42 [PATCH v2] NFSv4: Always ask for type with READDIR Benjamin Coddington
2023-08-30 20:10 ` Jeff Layton
2023-08-30 20:20 ` Trond Myklebust
2023-08-30 21:14 ` Jeff Layton
2023-08-31 15:17 ` Benjamin Coddington
2023-08-31 15:24 ` Jeff Layton
2023-08-31 18:41 ` Cedric Blancher
2023-08-31 18:53 ` Jeff Layton
2023-08-31 20:08 ` Rick Macklem
2023-08-31 21:33 ` Jeff Layton
2023-09-01 16:03 ` Chuck Lever III
2023-09-07 12:43 ` Benjamin Coddington [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-06 13:10 Benjamin Coddington
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=202D34A7-61AC-44DA-B2C1-CCE109EC2A76@redhat.com \
--to=bcodding@redhat.com \
--cc=anna@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@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