From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <wqu@suse.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-btrfs@vger.kernel.org, brauner@kernel.org,
djwong@kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] iomap: add IOMAP_DIO_FSBLOCK_ALIGNED flag
Date: Mon, 13 Oct 2025 21:58:25 -0700 [thread overview]
Message-ID: <aO3YcT9s8ezmIkzv@infradead.org> (raw)
In-Reply-To: <5a9e8670-c892-4b94-84a3-099096810678@suse.com>
On Tue, Oct 14, 2025 at 03:25:31PM +1030, Qu Wenruo wrote:
> Unfortunately that may not be that easy. Either we merge it early, meaning
> just this change + using the new flag in btrfs.
> But that means it makes no real change at all, as bs > ps direct IO is still
> disabled.
>
> Or we wait for the btrfs sub-block checksum handling patchset merged, then
> with the full bs > ps direct IO enablement.
> But that also means we're waiting for some other btrfs patches.
> There are already too many btrfs bs > ps patches pending now.
What's your plan for merging this? I was going to look into doing a
patch like this to improve the zoned XFS direct I/O handling soon,
so if you aim for 6.19 we need to figure out a way to get it into
the iomap tree and merge that into the xfs and btrfs trees. If you're
not aiming for 6.19 we could merge the iomap and xfs work through
either the iomap or xfs trees.
next prev parent reply other threads:[~2025-10-14 4:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 9:05 [PATCH v2] iomap: add IOMAP_DIO_FSBLOCK_ALIGNED flag Qu Wenruo
2025-10-13 11:14 ` Johannes Thumshirn
2025-10-13 20:39 ` Qu Wenruo
2025-10-14 4:36 ` Christoph Hellwig
2025-10-14 4:55 ` Qu Wenruo
2025-10-14 4:58 ` Christoph Hellwig [this message]
2025-10-14 5:10 ` Qu Wenruo
2025-10-16 12:10 ` Pankaj Raghav (Samsung)
2025-10-21 13:03 ` Christian Brauner
2025-10-22 7:23 ` Christoph Hellwig
2025-10-29 12:45 ` Christian Brauner
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=aO3YcT9s8ezmIkzv@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=wqu@suse.com \
/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