[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegsbaz+RRcukJEOw+H=G3ft43vjDMnJ8A24JiuZFQ24eHA@mail.gmail.com>
Date: Mon, 25 Apr 2022 15:41:49 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Jiachen Zhang <zhangjiachen.jaycee@...edance.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Xie Yongji <xieyongji@...edance.com>
Subject: Re: Re: [RFC PATCH] fuse: support cache revalidation in
writeback_cache mode
On Mon, 25 Apr 2022 at 15:33, Jiachen Zhang
<zhangjiachen.jaycee@...edance.com> wrote:
>
> On Mon, Apr 25, 2022 at 8:41 PM Miklos Szeredi <miklos@...redi.hu> wrote:
> >
> > On Fri, 25 Mar 2022 at 14:23, Jiachen Zhang
> > <zhangjiachen.jaycee@...edance.com> wrote:
> > >
> > > Hi all,
> > >
> > > This RFC patch implements attr cache and data cache revalidation for
> > > fuse writeback_cache mode in kernel. Looking forward to any suggestions
> > > or comments on this feature.
> >
> > Quick question before going into the details: could the cache
> > revalidation be done in the userspace filesystem instead, which would
> > set/clear FOPEN_KEEP_CACHE based on the result of the revalidation?
> >
> > Thanks,
> > Miklos
>
> Hi, Miklos,
>
> Thanks for replying. Yes, I believe we can also perform the
> revalidation in userspace, and we can invalidate the data cache with
> FOPEN_KEEP_CACHE cleared. But for now, there is no way we can
> invalidate attr cache (c/mtime and size) in writeback mode.
Can you please describe the use case for invalidating the attr cache?
Thanks,
Miklos
Powered by blists - more mailing lists