From: Luis Henriques <luis@igalia.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Bernd Schubert <bschubert@ddn.com>,
Dave Chinner <david@fromorbit.com>,
Matt Harvey <mharvey@jumptrading.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8] fuse: add more control over cache invalidation behaviour
Date: Thu, 13 Mar 2025 12:11:15 +0000 [thread overview]
Message-ID: <871pv1f7vg.fsf@igalia.com> (raw)
In-Reply-To: <CAJfpegtDBR4RMMOotxQC3d-pa38xNNB7ajfHrnpi_oQ0XWcTkA@mail.gmail.com> (Miklos Szeredi's message of "Thu, 13 Mar 2025 12:39:17 +0100")
On Thu, Mar 13 2025, Miklos Szeredi wrote:
> On Thu, 13 Mar 2025 at 12:25, Luis Henriques <luis@igalia.com> wrote:
>
>> Hmmm... And would you like this to be done in fuse? Or do you expect this
>> to me a more generic mechanism in dcache, available for other filesystems
>> as well?
>
> I don't know if this would be useful for anything else, so initially
> fuse specific.
>
> An list sorted by expiry time (implemented with an rbtree) would work,
> I think.
Great, thanks. As I said, I've added this to my TODO; once we have this
patch sorted out, I'll move into that. Thanks, Miklos.
Cheers,
--
Luís
next prev parent reply other threads:[~2025-03-13 12:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 9:14 [PATCH v8] fuse: add more control over cache invalidation behaviour Luis Henriques
2025-03-07 15:30 ` Luis Henriques
2025-03-10 16:42 ` Miklos Szeredi
2025-03-10 20:11 ` Bernd Schubert
2025-03-13 10:24 ` Miklos Szeredi
2025-03-11 11:08 ` Luis Henriques
2025-03-13 10:32 ` Miklos Szeredi
2025-03-13 11:25 ` Luis Henriques
2025-03-13 11:39 ` Miklos Szeredi
2025-03-13 12:11 ` Luis Henriques [this message]
2025-03-17 11:28 ` Luis Henriques
2025-04-11 15:14 ` Laura Promberger
2025-04-11 15:16 ` Laura Promberger
2025-04-15 10:34 ` Luis Henriques
2025-04-15 10:41 ` Miklos Szeredi
2025-04-15 10:49 ` 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=871pv1f7vg.fsf@igalia.com \
--to=luis@igalia.com \
--cc=bschubert@ddn.com \
--cc=david@fromorbit.com \
--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 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.