From: "Darrick J. Wong" <djwong@kernel.org>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3 6/8] xfs: only flush when COW fork blocks overlap data fork holes
Date: Mon, 9 Mar 2026 10:47:43 -0700 [thread overview]
Message-ID: <20260309174743.GP6033@frogsfrogsfrogs> (raw)
In-Reply-To: <20260309134506.167663-7-bfoster@redhat.com>
On Mon, Mar 09, 2026 at 09:45:04AM -0400, Brian Foster wrote:
> The zero range hole mapping flush case has been lifted from iomap
> into XFS. Now that we have more mapping context available from the
> ->iomap_begin() handler, we can isolate the flush further to when we
> know a hole is fronted by COW blocks.
>
> Rather than purely rely on pagecache dirty state, explicitly check
> for the case where a range is a hole in both forks. Otherwise trim
> to the range where there does happen to be overlap and use that for
> the pagecache writeback check. This might prevent some spurious
> zeroing, but more importantly makes it easier to remove the flush
> entirely.
>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Makes sense,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_iomap.c | 36 ++++++++++++++++++++++++++++++------
> 1 file changed, 30 insertions(+), 6 deletions(-)
>
> diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
> index 0f44d9aef25b..ce342b9ce2f0 100644
> --- a/fs/xfs/xfs_iomap.c
> +++ b/fs/xfs/xfs_iomap.c
> @@ -1781,10 +1781,12 @@ xfs_buffered_write_iomap_begin(
> {
> struct iomap_iter *iter = container_of(iomap, struct iomap_iter,
> iomap);
> + struct address_space *mapping = inode->i_mapping;
> struct xfs_inode *ip = XFS_I(inode);
> struct xfs_mount *mp = ip->i_mount;
> xfs_fileoff_t offset_fsb = XFS_B_TO_FSBT(mp, offset);
> xfs_fileoff_t end_fsb = xfs_iomap_end_fsb(mp, offset, count);
> + xfs_fileoff_t cow_fsb = NULLFILEOFF;
> struct xfs_bmbt_irec imap, cmap;
> struct xfs_iext_cursor icur, ccur;
> xfs_fsblock_t prealloc_blocks = 0;
> @@ -1852,6 +1854,8 @@ xfs_buffered_write_iomap_begin(
> }
> cow_eof = !xfs_iext_lookup_extent(ip, ip->i_cowfp, offset_fsb,
> &ccur, &cmap);
> + if (!cow_eof)
> + cow_fsb = cmap.br_startoff;
> }
>
> /* We never need to allocate blocks for unsharing a hole. */
> @@ -1866,17 +1870,37 @@ xfs_buffered_write_iomap_begin(
> * writeback to remap pending blocks and restart the lookup.
> */
> if ((flags & IOMAP_ZERO) && imap.br_startoff > offset_fsb) {
> - if (filemap_range_needs_writeback(inode->i_mapping, offset,
> - offset + count - 1)) {
> + loff_t start, end;
> +
> + imap.br_blockcount = imap.br_startoff - offset_fsb;
> + imap.br_startoff = offset_fsb;
> + imap.br_startblock = HOLESTARTBLOCK;
> + imap.br_state = XFS_EXT_NORM;
> +
> + if (cow_fsb == NULLFILEOFF)
> + goto found_imap;
> + if (cow_fsb > offset_fsb) {
> + xfs_trim_extent(&imap, offset_fsb,
> + cow_fsb - offset_fsb);
> + goto found_imap;
> + }
> +
> + /* COW fork blocks overlap the hole */
> + xfs_trim_extent(&imap, offset_fsb,
> + cmap.br_startoff + cmap.br_blockcount - offset_fsb);
> + start = XFS_FSB_TO_B(mp, imap.br_startoff);
> + end = XFS_FSB_TO_B(mp,
> + imap.br_startoff + imap.br_blockcount) - 1;
> + if (filemap_range_needs_writeback(mapping, start, end)) {
> xfs_iunlock(ip, lockmode);
> - error = filemap_write_and_wait_range(inode->i_mapping,
> - offset, offset + count - 1);
> + error = filemap_write_and_wait_range(mapping, start,
> + end);
> if (error)
> return error;
> goto restart;
> }
> - xfs_hole_to_iomap(ip, iomap, offset_fsb, imap.br_startoff);
> - goto out_unlock;
> +
> + goto found_imap;
> }
>
> /*
> --
> 2.52.0
>
>
next prev parent reply other threads:[~2026-03-09 17:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 13:44 [PATCH v3 0/8] iomap, xfs: improve zero range flushing and lookup Brian Foster
2026-03-09 13:44 ` [PATCH v3 1/8] xfs: fix iomap hole map reporting for zoned zero range Brian Foster
2026-03-09 17:11 ` Darrick J. Wong
2026-03-09 18:18 ` Brian Foster
2026-03-10 14:47 ` Darrick J. Wong
2026-03-10 6:45 ` Christoph Hellwig
2026-03-09 13:45 ` [PATCH v3 2/8] xfs: flush dirty pagecache over hole in zoned mode " Brian Foster
2026-03-09 17:22 ` Darrick J. Wong
2026-03-09 18:19 ` Brian Foster
2026-03-10 6:47 ` Christoph Hellwig
2026-03-10 14:48 ` Darrick J. Wong
2026-03-10 6:45 ` Christoph Hellwig
2026-03-09 13:45 ` [PATCH v3 3/8] iomap, xfs: lift zero range hole mapping flush into xfs Brian Foster
2026-03-09 17:40 ` Darrick J. Wong
2026-03-10 6:47 ` Christoph Hellwig
2026-03-09 13:45 ` [PATCH v3 4/8] xfs: flush eof folio before insert range size update Brian Foster
2026-03-09 17:32 ` Darrick J. Wong
2026-03-09 18:24 ` Brian Foster
2026-03-09 13:45 ` [PATCH v3 5/8] xfs: look up cow fork extent earlier for buffered iomap_begin Brian Foster
2026-03-09 13:45 ` [PATCH v3 6/8] xfs: only flush when COW fork blocks overlap data fork holes Brian Foster
2026-03-09 17:47 ` Darrick J. Wong [this message]
2026-03-09 13:45 ` [PATCH v3 7/8] xfs: replace zero range flush with folio batch Brian Foster
2026-03-09 17:48 ` Darrick J. Wong
2026-03-09 13:45 ` [PATCH v3 8/8] xfs: report cow mappings with dirty pagecache for iomap zero range Brian Foster
2026-03-09 17:56 ` Darrick J. Wong
2026-03-09 18:31 ` Brian Foster
2026-03-09 18:38 ` Darrick J. Wong
2026-03-10 6:50 ` Christoph Hellwig
2026-03-10 14:52 ` Darrick J. Wong
2026-03-10 14:59 ` Christoph Hellwig
2026-03-10 6:49 ` Christoph Hellwig
2026-03-10 6:45 ` [PATCH v3 0/8] iomap, xfs: improve zero range flushing and lookup Christoph Hellwig
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=20260309174743.GP6033@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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