All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org,
	fuse-devel <fuse-devel@lists.sourceforge.net>
Subject: Re: [fuse-devel] [fuse] Speeding up readdir()
Date: Fri, 07 Dec 2018 13:39:00 +0000	[thread overview]
Message-ID: <87woolsbgr.fsf@vostro.rath.org> (raw)
In-Reply-To: <CAJfpegstGc5YqdO_duiWJkCVjiVMbJV2e=z4ZrhFzz7Lq=-Jtw@mail.gmail.com> (Miklos Szeredi's message of "Fri, 7 Dec 2018 14:04:32 +0100")

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.

I was actually confusing LOOKUP requests and GETATTR requests. I assume
the GETATTR requests would be explained by atime invalidation?


Best,
-Nikolaus

-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

  parent reply	other threads:[~2018-12-07 13:39 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
2018-12-07 13:39       ` Nikolaus Rath [this message]
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=87woolsbgr.fsf@vostro.rath.org \
    --to=nikolaus@rath.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.