From: Daire Byrne <daire@dneg.com>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: directory caching & negative file lookups?
Date: Thu, 1 Sep 2022 16:27:43 +0100 [thread overview]
Message-ID: <CAPt2mGMOSHssr_J6bcf8A8dnU_oHNf_UuHZsDk1WxVi=TUheWA@mail.gmail.com> (raw)
In-Reply-To: <a4abb5fcf94d706cc3f47d6b629763d5b1831c21.camel@hammerspace.com>
On Thu, 1 Sept 2022 at 14:55, Trond Myklebust <trondmy@hammerspace.com> wrote:
> man 5 nfs
>
> Look for the section on the 'lookupcache=mode' mount option.
So I get that the client caches negative lookups once we've made them
(the default lookupcache=all), but what I'm wondering is if we have
already cached the entire directory contents before the (negative)
lookup, can we not reply that it doesn't exist using that information
without having to go across the wire the at all (even the first time)?
Or is there no concept of "cached directory contents"? I thought that
maybe readdir/readdirplus knew about the "full contents" of a
directory?
My thinking was that if we did a readdir/readirplus first, we could
then do lookups for any random non-existent filename without having to
send anything across the wire. Like I said, a newbie question with
limited understanding of the actual internals :)
Daire
next prev parent reply other threads:[~2022-09-01 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 13:32 directory caching & negative file lookups? Daire Byrne
2022-09-01 13:55 ` Trond Myklebust
2022-09-01 15:27 ` Daire Byrne [this message]
2022-09-01 15:43 ` Trond Myklebust
2022-09-01 15:49 ` Daire Byrne
2024-04-05 14:47 ` Daire Byrne
2024-04-05 15:03 ` Trond Myklebust
2024-04-12 9:11 ` Daire Byrne
2024-04-12 10:21 ` Jeff Layton
2024-04-12 11:43 ` Daire Byrne
2024-04-12 14:13 ` 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='CAPt2mGMOSHssr_J6bcf8A8dnU_oHNf_UuHZsDk1WxVi=TUheWA@mail.gmail.com' \
--to=daire@dneg.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).