From: Luis Henriques <luis@igalia.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Bernd Schubert <bernd@bsbernd.com>,
Laura Promberger <laura.promberger@cern.ch>,
Dave Chinner <david@fromorbit.com>,
Matt Harvey <mharvey@jumptrading.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] fuse: new workqueue to periodically invalidate expired dentries
Date: Wed, 02 Jul 2025 17:35:33 +0100 [thread overview]
Message-ID: <87bjq2k0tm.fsf@igalia.com> (raw)
In-Reply-To: <CAJfpegue3szRGZs+ogvYjiVt0YUo-=e+hrj-r=8ZDy11Zgrt9w@mail.gmail.com> (Miklos Szeredi's message of "Wed, 2 Jul 2025 17:39:58 +0200")
On Wed, Jul 02 2025, Miklos Szeredi wrote:
> On Tue, 20 May 2025 at 17:42, Luis Henriques <luis@igalia.com> wrote:
>>
>> This patch adds a new module parameter 'inval_wq' which is used to start a
>> workqueue to periodically invalidate expired dentries. The value of this
>> new parameter is the period, in seconds, of the workqueue. When it is set,
>> every new dentry will be added to an rbtree, sorted by the dentry's expiry
>> time.
>>
>> When the workqueue is executed, it will check the dentries in this tree and
>> invalidate them if:
>>
>> - The dentry has timed-out, or if
>> - The connection epoch has been incremented.
>
> I wonder, why not make the whole infrastructure global? There's no
> reason to have separate rb-trees and workqueues for each fuse
> instance.
Hmm... true. My initial approach was to use a mount parameter to enabled
it for each connection. When you suggested replacing that by a module
parameter, I should have done that too.
> Contention on the lock would be worse, but it's bad as it
> is, so need some solution, e.g. hashed lock, which is better done with
> a single instance.
Right, I'll think how to fix it (or at least reduce contention).
>> The workqueue will run for, at most, 5 seconds each time. It will
>> reschedule itself if the dentries tree isn't empty.
>
> It should check need_resched() instead.
OK.
>> diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
>> index 1fb0b15a6088..257ca2b36b94 100644
>> --- a/fs/fuse/dir.c
>> +++ b/fs/fuse/dir.c
>> @@ -34,33 +34,153 @@ static void fuse_advise_use_readdirplus(struct inode *dir)
>> set_bit(FUSE_I_ADVISE_RDPLUS, &fi->state);
>> }
>>
>> -#if BITS_PER_LONG >= 64
>> -static inline void __fuse_dentry_settime(struct dentry *entry, u64 time)
>> +struct fuse_dentry {
>> + u64 time;
>> + struct rcu_head rcu;
>> + struct rb_node node;
>> + struct dentry *dentry;
>> +};
>> +
>
> You lost the union with rcu_head. Any other field is okay, none of
> them matter in rcu protected code. E.g.
>
> struct fuse_dentry {
> u64 time;
> union {
> struct rcu_head rcu;
> struct rb_node node;
> };
> struct dentry *dentry;
> };
Oops. I'll fix that.
Thanks a lot for your feedback, Miklos. Much appreciated. I'll re-work
this patch and send a new revision shortly.
Cheers,
--
Luís
next prev parent reply other threads:[~2025-07-02 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 15:42 Luis Henriques
2025-06-13 15:53 ` Luis Henriques
2025-07-02 15:39 ` Miklos Szeredi
2025-07-02 16:35 ` Luis Henriques [this message]
2025-07-03 12:46 ` Luis Henriques
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=87bjq2k0tm.fsf@igalia.com \
--to=luis@igalia.com \
--cc=bernd@bsbernd.com \
--cc=david@fromorbit.com \
--cc=laura.promberger@cern.ch \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mharvey@jumptrading.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®