[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegui8-_J3o1QKOxGqMKOSt5O6Xw979YnnmwTF3P0yh_j+Q@mail.gmail.com>
Date: Mon, 23 Jun 2025 15:16:53 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Amir Goldstein <amir73il@...il.com>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, John@...ves.net,
bernd@...ernd.com, joannelkoong@...il.com, Josef Bacik <josef@...icpanda.com>,
linux-ext4 <linux-ext4@...r.kernel.org>, "Theodore Ts'o" <tytso@....edu>,
Matthew Wilcox <willy@...radead.org>
Subject: Re: [RFC[RAP] V2] fuse: use fs-iomap for better performance so we can
containerize ext4
On Fri, 13 Jun 2025 at 19:37, Darrick J. Wong <djwong@...nel.org> wrote:
> Top of that list is timestamps and file attributes, because fuse no
> longer calls the fuse server for file writes. As a result, the kernel
> inode always has the most uptodate versions of the some file attributes
> (i_size, timestamps, mode) and just want to send FUSE_SETATTR whenever
> the dirty inode gets flushed.
This is already the case for cached writes, no new code should be needed.
Thanks,
Miklos
Powered by blists - more mailing lists