From: Kinglong Mee <kinglongmee@gmail.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: Anna Schumaker <anna@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Trond Myklebust <trondmy@hammerspace.com>
Subject: Re: [PATCH] nfs: fix redundant readdir request after get eof
Date: Sat, 15 Jul 2023 20:06:28 +0800 [thread overview]
Message-ID: <CAB6yy36uWjnay8OTbZCvHGNih8mjCASc7yDnNeDp2KqxfA8Dzw@mail.gmail.com> (raw)
In-Reply-To: <70B9A332-FDA0-418E-81CF-962229E93AC5@redhat.com>
On Fri, Jul 14, 2023 at 11:19 PM Benjamin Coddington
<bcodding@redhat.com> wrote:
>
> On 13 Jul 2023, at 23:07, Kinglong Mee wrote:
>
> > Hi Ben,
> >
> ...
> > Comparing with the above one, this seems work.
>
> This fixes it for me and keeps the optimization. Its quite a subtle bit of
> logic - maybe a comment is appropriate?
Thanks for your testing.
I will send a new patch with a comment.
>
> One non-intuitive thing here is
> that array->size == 19 for a directory with 18 entries, since we count the
> "eof" entry as a blank entry instead of the last real entry.
No.
This is not a blank entry, every entry is a real one.
For the first emit, only returns 18 entries to the caller,
the next emit will return the 19th one.
thanks,
Kinglong Mee
prev parent reply other threads:[~2023-07-15 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 14:52 [PATCH] nfs: fix redundant readdir request after get eof Kinglong Mee
2023-07-13 19:17 ` Benjamin Coddington
[not found] ` <CAB6yy359Gvdu=v1ZvTLXPoY2EMtER3_cBVDKc4MQYhaMOjcUSw@mail.gmail.com>
2023-07-14 15:19 ` Benjamin Coddington
2023-07-15 12:06 ` Kinglong Mee [this message]
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=CAB6yy36uWjnay8OTbZCvHGNih8mjCASc7yDnNeDp2KqxfA8Dzw@mail.gmail.com \
--to=kinglongmee@gmail.com \
--cc=anna@kernel.org \
--cc=bcodding@redhat.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;
as well as URLs for NNTP newsgroup(s).