From: Miklos Szeredi <miklos@szeredi.hu>
To: "Junichi Uekawa (上川純一)" <uekawa@google.com>
Cc: Keiichi Watanabe <keiichiw@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
mhiramat@google.com, takayas@chromium.org, drosen@google.com,
sarthakkukreti@google.com, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/3] fuse: Add negative_dentry_timeout option
Date: Wed, 21 Jun 2023 06:07:30 +0200 [thread overview]
Message-ID: <CAJfpegtNjAELur_AtqiGdO6LJRDyT+WQ1UKtG-o=Em0rAhOKMg@mail.gmail.com> (raw)
In-Reply-To: <CADgJSGGDeu_dPduBuK7N324oJ9641VKv2+fAVAbDY=-itsFjEQ@mail.gmail.com>
On Wed, 21 Jun 2023 at 00:53, Junichi Uekawa (上川純一) <uekawa@google.com> wrote:
>
> Hi
>
>
>
> 2023年6月21日(水) 4:28 Miklos Szeredi <miklos@szeredi.hu>:
>>
>> On Tue, 20 Jun 2023 at 17:14, Keiichi Watanabe <keiichiw@chromium.org> wrote:
>> >
>> > Add `negative_dentry_timeout` mount option for FUSE to cache negative
>> > dentries for the specified duration.
>>
>> This is already possible, no kernel changes needed. See e.g.
>> xmp_init() in libfuse/example/passthrough.c.
>>
>
> Thank you for the pointer!
>
> So reading libfuse/fuse.c, fuse_lib_lookup does a reply with e.ino=0 err=0 (instead of ENOENT) with e.entry_timeout=negative_timeout,
> for each lookup (and there's no global configuration but that's okay) ?
Yes.
Thanks,
Miklos
next prev parent reply other threads:[~2023-06-21 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 15:13 [PATCH 0/3] Support negative dentry cache for FUSE and virtiofs Keiichi Watanabe
2023-06-20 15:13 ` [PATCH 1/3] docs: virtiofs: Fix descriptions about virtiofs mount option Keiichi Watanabe
2023-06-20 15:13 ` [PATCH 2/3] fuse: Add negative_dentry_timeout option Keiichi Watanabe
2023-06-20 19:28 ` Miklos Szeredi
[not found] ` <CADgJSGGDeu_dPduBuK7N324oJ9641VKv2+fAVAbDY=-itsFjEQ@mail.gmail.com>
2023-06-21 4:07 ` Miklos Szeredi [this message]
2023-06-21 9:40 ` Keiichi Watanabe
2023-06-20 15:13 ` [PATCH 3/3] virtiofs: " Keiichi Watanabe
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='CAJfpegtNjAELur_AtqiGdO6LJRDyT+WQ1UKtG-o=Em0rAhOKMg@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=corbet@lwn.net \
--cc=drosen@google.com \
--cc=keiichiw@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@google.com \
--cc=sarthakkukreti@google.com \
--cc=takayas@chromium.org \
--cc=uekawa@google.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).