linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: linux-fsdevel@vger.kernel.org,
	fuse-devel <fuse-devel@lists.sourceforge.net>
Subject: Re: [fuse-devel] [fuse] Speeding up readdir()
Date: Fri, 7 Dec 2018 14:18:58 +0100	[thread overview]
Message-ID: <CAJfpegsOnOhzt2F3LSFSeZ148a8eZ_2JBdHkaBhKX43Egm1kTQ@mail.gmail.com> (raw)
In-Reply-To: <875zw5tr7i.fsf@vostro.rath.org>

On Fri, Dec 7, 2018 at 2:13 PM Nikolaus Rath <Nikolaus@rath.org> wrote:
>
> On Dec 07 2018, Miklos Szeredi <miklos@szeredi.hu> wrote:
> > On Fri, Dec 7, 2018 at 1:55 PM Nikolaus Rath <Nikolaus@rath.org> wrote:
> >
> >> I am not 100% sure because of the atime invalidation issue. Apart from
> >> that, it definitely was not timed out.
> >
> > The atime invalidation is different because that never results in
> > LOOKUP requests being generated.
> >
> >> Are you saying that I should not be seeing lookup() requests after
> >> (non-plus) readdir() if the dentry is already cached?
> >
> > If the dentry is already cached, and the timeout has not expired, then
> > you shouldn't see LOOKUP requests for that dentry.
> >
> > Hmm, I see some strange entry invalidation calls in NFS export.  Do
> > you know if there's NFS export or open_by_handle(2) calls?
>
> Definitely no NFS export. I can't say for sure about open_by_handle, I
> do not have the source code of the client application.

Anyway, a debug log might give some ideas; could you please send one
with the weird behaviror?

Thanks,
Miklos

  reply	other threads:[~2018-12-07 13:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 20:00 [fuse] Speeding up readdir() Nikolaus Rath
2018-12-07  9:21 ` Miklos Szeredi
2018-12-07 12:55   ` [fuse-devel] " Nikolaus Rath
2018-12-07 13:04     ` Miklos Szeredi
2018-12-07 13:13       ` Nikolaus Rath
2018-12-07 13:18         ` Miklos Szeredi [this message]
2018-12-07 13:39       ` Nikolaus Rath
2018-12-10  9:31         ` Miklos Szeredi
2018-12-07 13:38   ` Nikolaus Rath

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=CAJfpegsOnOhzt2F3LSFSeZ148a8eZ_2JBdHkaBhKX43Egm1kTQ@mail.gmail.com \
    --to=miklos@szeredi.hu \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).