linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <wqu@suse.com>
Cc: 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:36:50 -0700	[thread overview]
Message-ID: <aO3TYhXo1LDxsd5_@infradead.org> (raw)
In-Reply-To: <c78d08f4e709158f30e1e88e62ab98db45dd7883.1760345826.git.wqu@suse.com>

On Mon, Oct 13, 2025 at 07:35:16PM +1030, Qu Wenruo wrote:
> - Remove the btrfs part that utilize the new flag
>   Now it's in the enablement patch of btrfs' bs > ps direct IO support.

I didn't really suggest removing it, but splitting it into a separate
patch in a two-patch series.  We could probably even move everything
through the btrfs tree for 6.18 to get the fix in.  It's just important
to keep infrastructure and user separate if you have to e.g. revert the
btrfs part for some reason, but we have another user in the meantime.
And I plan to use this for zoned XFS soon.

> +	/*
> +	 * Align to the larger one of bdev and fs block size, to meet the
> +	 * alignment requirement of both layers.
> +	 */
> +	if (dio->flags & IOMAP_DIO_FSBLOCK_ALIGNED)
> +		alignment = max(alignment, fs_block_size);
> +

This looks much nicer, and thanks for the explanation!

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>

  parent reply	other threads:[~2025-10-14  4:36 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 [this message]
2025-10-14  4:55   ` Qu Wenruo
2025-10-14  4:58     ` Christoph Hellwig
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=aO3TYhXo1LDxsd5_@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;
as well as URLs for NNTP newsgroup(s).