From: Andrew Price <anprice@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel@vger.kernel.org, gfs2@lists.linux.dev,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: refactor the iomap writeback code v2
Date: Thu, 26 Jun 2025 15:59:54 +0100 [thread overview]
Message-ID: <07ef2fd5-d4cb-4fc3-8917-4bd6f06501d0@redhat.com> (raw)
In-Reply-To: <20250617105514.3393938-1-hch@lst.de>
On 17/06/2025 11:54, Christoph Hellwig wrote:
> Hi all,
>
> this is an alternative approach to the writeback part of the
> "fuse: use iomap for buffered writes + writeback" series from Joanne.
> It doesn't try to make the code build without CONFIG_BLOCK yet.
>
> The big difference compared to Joanne's version is that I hope the
> split between the generic and ioend/bio based writeback code is a bit
> cleaner here. We have two methods that define the split between the
> generic writeback code, and the implemementation of it, and all knowledge
> of ioends and bios now sits below that layer.
>
> This version passes basic testing on xfs, and gets as far as mainline
> for gfs2 (crashes in generic/361).
I can't get generic/361 to crash per se, but it does fail as it detects the new warning about the missing ->migrate_folio for the gfs2_{rgrp,meta}_aops, which I'm looking at now.
If you have different results to this, please let me know more about the crash and your test environment.
Thanks,
Andy
>
> Changes since v1:
> - fix iomap reuse in block/zonefs/gfs2
> - catch too large return value from ->writeback_range
> - mention the correct file name in a commit log
> - add patches for folio laundering
> - add patches for read/modify write in the generic write helpers
>
> Diffstat:
> Documentation/filesystems/iomap/design.rst | 3
> Documentation/filesystems/iomap/operations.rst | 51 --
> block/fops.c | 37 +-
> fs/gfs2/aops.c | 8
> fs/gfs2/bmap.c | 48 +-
> fs/gfs2/bmap.h | 1
> fs/gfs2/file.c | 3
> fs/iomap/buffered-io.c | 438 ++++++-------------------
> fs/iomap/internal.h | 1
> fs/iomap/ioend.c | 220 ++++++++++++
> fs/iomap/trace.h | 2
> fs/xfs/xfs_aops.c | 238 +++++++------
> fs/xfs/xfs_file.c | 6
> fs/xfs/xfs_iomap.c | 12
> fs/xfs/xfs_iomap.h | 1
> fs/xfs/xfs_reflink.c | 3
> fs/zonefs/file.c | 40 +-
> include/linux/iomap.h | 81 ++--
> 18 files changed, 630 insertions(+), 563 deletions(-)
>
next prev parent reply other threads:[~2025-06-26 15:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 10:54 refactor the iomap writeback code v2 Christoph Hellwig
2025-06-17 10:55 ` [PATCH 01/11] iomap: pass more arguments using struct iomap_writepage_ctx Christoph Hellwig
2025-06-17 17:54 ` Joanne Koong
2025-06-18 4:35 ` Christoph Hellwig
2025-06-17 10:55 ` [PATCH 02/11] iomap: cleanup the pending writeback tracking in iomap_writepage_map_blocks Christoph Hellwig
2025-06-17 10:55 ` [PATCH 03/11] iomap: refactor the writeback interface Christoph Hellwig
2025-06-17 18:33 ` Joanne Koong
2025-06-18 4:39 ` Christoph Hellwig
2025-06-17 10:55 ` [PATCH 04/11] iomap: hide ioends from the generic writeback code Christoph Hellwig
2025-06-17 19:22 ` Joanne Koong
2025-06-18 4:41 ` Christoph Hellwig
2025-06-17 10:55 ` [PATCH 05/11] iomap: add public helpers for uptodate state manipulation Christoph Hellwig
2025-06-17 10:55 ` [PATCH 06/11] iomap: move all ioend handling to ioend.c Christoph Hellwig
2025-06-17 19:35 ` Joanne Koong
2025-06-17 10:55 ` [PATCH 07/11] iomap: rename iomap_writepage_map to iomap_writeback_folio Christoph Hellwig
2025-06-17 19:44 ` Joanne Koong
2025-06-18 4:42 ` Christoph Hellwig
2025-06-17 10:55 ` [PATCH 08/11] iomap: move folio_unlock out of iomap_writeback_folio Christoph Hellwig
2025-06-17 10:55 ` [PATCH 09/11] iomap: export iomap_writeback_folio Christoph Hellwig
2025-06-17 22:00 ` Joanne Koong
2025-06-17 10:55 ` [PATCH 10/11] iomap: replace iomap_folio_ops with iomap_write_ops Christoph Hellwig
2025-06-17 22:25 ` Joanne Koong
2025-06-18 4:43 ` Christoph Hellwig
2025-06-17 10:55 ` [PATCH 11/11] iomap: add read_folio_range() handler for buffered writes Christoph Hellwig
2025-06-26 14:59 ` Andrew Price [this message]
2025-06-27 7:02 ` refactor the iomap writeback code v2 Christoph Hellwig
2025-07-07 12:07 ` Andrew Price
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=07ef2fd5-d4cb-4fc3-8917-4bd6f06501d0@redhat.com \
--to=anprice@redhat.com \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-fsdevel@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