Linux Documentation
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Joanne Koong <joannelkoong@gmail.com>,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-block@vger.kernel.org,
	gfs2@lists.linux.dev
Subject: Re: refactor the iomap writeback code v5
Date: Mon, 14 Jul 2025 10:52:07 +0200	[thread overview]
Message-ID: <20250714-untiefen-zonen-36da5ea68518@brauner> (raw)
In-Reply-To: <20250710133343.399917-1-hch@lst.de>

On Thu, 10 Jul 2025 15:33:24 +0200, Christoph Hellwig wrote:
> 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.

I dropped that sentence from the merge commit.

> 
> 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.
> 
> [...]

Applied to the vfs-6.17.iomap branch of the vfs/vfs.git tree.
Patches in the vfs-6.17.iomap branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.17.iomap

[01/14] iomap: header diet
        https://git.kernel.org/vfs/vfs/c/8cd0a39cab56
[02/14] iomap: pass more arguments using the iomap writeback context
        https://git.kernel.org/vfs/vfs/c/67fd9615a782
[03/14] iomap: cleanup the pending writeback tracking in iomap_writepage_map_blocks
        https://git.kernel.org/vfs/vfs/c/40368a6acb95
[04/14] iomap: refactor the writeback interface
        https://git.kernel.org/vfs/vfs/c/fb7399cf2d0b
[05/14] iomap: hide ioends from the generic writeback code
        https://git.kernel.org/vfs/vfs/c/f4fa7981fa26
[06/14] iomap: add public helpers for uptodate state manipulation
        https://git.kernel.org/vfs/vfs/c/9caf1ea80ced
[07/14] iomap: move all ioend handling to ioend.c
        https://git.kernel.org/vfs/vfs/c/8f02cecd80b9
[08/14] iomap: rename iomap_writepage_map to iomap_writeback_folio
        https://git.kernel.org/vfs/vfs/c/58f0d5a30427
[09/14] iomap: move folio_unlock out of iomap_writeback_folio
        https://git.kernel.org/vfs/vfs/c/f8b6a94a4cca
[10/14] iomap: export iomap_writeback_folio
        https://git.kernel.org/vfs/vfs/c/8b217cf779cb
[11/14] iomap: replace iomap_folio_ops with iomap_write_ops
        https://git.kernel.org/vfs/vfs/c/2a5574fc57d1
[12/14] iomap: improve argument passing to iomap_read_folio_sync
        https://git.kernel.org/vfs/vfs/c/e6caf01d3f57
[13/14] iomap: add read_folio_range() handler for buffered writes
        https://git.kernel.org/vfs/vfs/c/c5690dd01978
[14/14] iomap: build the writeback code without CONFIG_BLOCK
        https://git.kernel.org/vfs/vfs/c/5699b7e21d20

      parent reply	other threads:[~2025-07-14  8:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 13:33 refactor the iomap writeback code v5 Christoph Hellwig
2025-07-10 13:33 ` [PATCH 01/14] iomap: header diet Christoph Hellwig
2025-07-10 13:33 ` [PATCH 02/14] iomap: pass more arguments using the iomap writeback context Christoph Hellwig
2025-07-10 13:33 ` [PATCH 03/14] iomap: cleanup the pending writeback tracking in iomap_writepage_map_blocks Christoph Hellwig
2025-07-10 13:33 ` [PATCH 04/14] iomap: refactor the writeback interface Christoph Hellwig
2025-07-10 13:33 ` [PATCH 05/14] iomap: hide ioends from the generic writeback code Christoph Hellwig
2025-07-10 13:33 ` [PATCH 06/14] iomap: add public helpers for uptodate state manipulation Christoph Hellwig
2025-07-10 13:33 ` [PATCH 07/14] iomap: move all ioend handling to ioend.c Christoph Hellwig
2025-07-10 13:33 ` [PATCH 08/14] iomap: rename iomap_writepage_map to iomap_writeback_folio Christoph Hellwig
2025-07-10 13:33 ` [PATCH 09/14] iomap: move folio_unlock out of iomap_writeback_folio Christoph Hellwig
2025-07-10 13:33 ` [PATCH 10/14] iomap: export iomap_writeback_folio Christoph Hellwig
2025-07-10 13:33 ` [PATCH 11/14] iomap: replace iomap_folio_ops with iomap_write_ops Christoph Hellwig
2025-07-10 13:33 ` [PATCH 12/14] iomap: improve argument passing to iomap_read_folio_sync Christoph Hellwig
2025-07-10 13:33 ` [PATCH 13/14] iomap: add read_folio_range() handler for buffered writes Christoph Hellwig
2025-07-10 13:33 ` [PATCH 14/14] iomap: build the writeback code without CONFIG_BLOCK Christoph Hellwig
2025-07-11  9:50 ` refactor the iomap writeback code v5 Christian Brauner
2025-07-11 11:20   ` Christoph Hellwig
2025-07-14  8:52 ` Christian Brauner [this message]

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=20250714-untiefen-zonen-36da5ea68518@brauner \
    --to=brauner@kernel.org \
    --cc=djwong@kernel.org \
    --cc=gfs2@lists.linux.dev \
    --cc=hch@lst.de \
    --cc=joannelkoong@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --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