From: Luis Chamberlain <mcgrof@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
lsf-pc@lists.linux-foundation.org,
Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>,
"kbus >> Keith Busch" <kbusch@kernel.org>,
Pankaj Raghav <p.raghav@samsung.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: LSF/MM/BPF 2023 IOMAP conversion status update
Date: Mon, 27 Feb 2023 12:24:51 -0800 [thread overview]
Message-ID: <Y/0RkzEv8ysuXntk@bombadil.infradead.org> (raw)
In-Reply-To: <Y/0IzG4S2l52oC7R@magnolia>
On Mon, Feb 27, 2023 at 11:47:24AM -0800, Darrick J. Wong wrote:
> OTOH, it also means that we've learned the hard way that pagecache
> operations need a means to revalidate mappings to avoid write races.
> This applies both to the initial pagecache write and to scheduling
> writeback, but the mechanisms for each were developed separately and
> years apart. See iomap::validity_cookie and
> xfs_writepage_ctx::{data,cow}_seq for what I'm talking about.
> We (xfs developers) ought to figure out if these two mechanisms should
> be merged before more filesystems start using iomap for buffered io.
That puts a good yield notice to some conversion efforts, thanks, this
already alone is very useulf.
> I'd like to have a discussion about how to clean up and clarify the
> iomap interfaces, and a separate one about how to port the remaining 35+
> filesystems. I don't know how exactly to split this into LSF sessions,
> other than to suggest at least two.
From a conversion perspective, ideally if it was obvious I think we
should be able to do some of it ala coccinelle, but I have yet to see
any remotely obvious pattern. And it makes me wonder, should we strive
to make the conversion as painless / obvious ? Is that a good litmus
for when we should be ready to start converting other filesystems?
> If hch or dchinner show up, I also want to drag them into this. :)
And here I've been thinking I had to go to Australia to see you all together.
Luis
next prev parent reply other threads:[~2023-02-27 20:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 4:46 Luis Chamberlain
2023-01-29 5:06 ` Matthew Wilcox
2023-01-29 5:39 ` Luis Chamberlain
2023-02-08 16:04 ` Jan Kara
2023-02-24 7:01 ` Zhang Yi
2023-02-26 20:16 ` Ritesh Harjani
2023-03-16 14:40 ` [RFCv1][WIP] ext2: Move direct-io to use iomap Ritesh Harjani (IBM)
2023-03-16 15:41 ` Darrick J. Wong
2023-03-20 16:11 ` Ritesh Harjani
2023-03-20 13:15 ` Christoph Hellwig
2023-03-20 17:51 ` Jan Kara
2023-03-22 6:34 ` Ritesh Harjani
2023-03-23 11:30 ` Jan Kara
2023-03-23 13:19 ` Ritesh Harjani
2023-03-30 0:02 ` Christoph Hellwig
2023-02-27 19:26 ` LSF/MM/BPF 2023 IOMAP conversion status update Darrick J. Wong
2023-02-27 21:02 ` Matthew Wilcox
2023-02-27 19:47 ` Darrick J. Wong
2023-02-27 20:24 ` Luis Chamberlain [this message]
2023-02-27 19:06 ` Darrick J. Wong
2023-02-27 19:58 ` Luis Chamberlain
2023-03-01 16:59 ` Ritesh Harjani
2023-03-01 17:08 ` Darrick J. Wong
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=Y/0RkzEv8ysuXntk@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=p.raghav@samsung.com \
--cc=willy@infradead.org \
/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