From: Christoph Hellwig <hch@lst.de>
To: linux-mm@kvack.org
Cc: Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.com>,
David Howells <dhowells@redhat.com>,
Brian Foster <bfoster@redhat.com>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: convert write_cache_pages() to an iterator v8
Date: Mon, 19 Feb 2024 07:28:41 +0100 [thread overview]
Message-ID: <20240219062841.GA4410@lst.de> (raw)
In-Reply-To: <20240215063649.2164017-1-hch@lst.de>
Now that we've got all the reviews it would be good to think about
queuing up the series. Look like page-writeback.c usually goes through
the mm tree, and that seems good for this series as well. Andrew?
prev parent reply other threads:[~2024-02-19 6:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 6:36 convert write_cache_pages() to an iterator v8 Christoph Hellwig
2024-02-15 6:36 ` [PATCH 01/14] writeback: don't call mapping_set_error on AOP_WRITEPAGE_ACTIVATE Christoph Hellwig
2024-02-15 9:31 ` Jan Kara
2024-02-15 11:44 ` Brian Foster
2024-02-15 6:36 ` [PATCH 02/14] writeback: remove a duplicate prototype for tag_pages_for_writeback Christoph Hellwig
2024-02-15 6:36 ` [PATCH 03/14] writeback: fix done_index when hitting the wbc->nr_to_write Christoph Hellwig
2024-02-15 6:36 ` [PATCH 04/14] writeback: also update wbc->nr_to_write on writeback failure Christoph Hellwig
2024-02-15 6:36 ` [PATCH 05/14] writeback: only update ->writeback_index for range_cyclic writeback Christoph Hellwig
2024-02-15 6:36 ` [PATCH 06/14] writeback: rework the loop termination condition in write_cache_pages Christoph Hellwig
2024-02-15 6:36 ` [PATCH 07/14] writeback: Factor folio_prepare_writeback() out of write_cache_pages() Christoph Hellwig
2024-02-15 6:36 ` [PATCH 08/14] writeback: Factor writeback_get_batch() " Christoph Hellwig
2024-02-15 6:36 ` [PATCH 09/14] writeback: Simplify the loops in write_cache_pages() Christoph Hellwig
2024-02-15 6:36 ` [PATCH 10/14] pagevec: Add ability to iterate a queue Christoph Hellwig
2024-02-15 6:36 ` [PATCH 11/14] writeback: Use the folio_batch queue iterator Christoph Hellwig
2024-02-15 6:36 ` [PATCH 12/14] writeback: Move the folio_prepare_writeback loop out of write_cache_pages() Christoph Hellwig
2024-02-15 6:36 ` [PATCH 13/14] writeback: add a writeback iterator Christoph Hellwig
2024-02-15 6:36 ` [PATCH 14/14] writeback: Remove a use of write_cache_pages() from do_writepages() Christoph Hellwig
2024-02-19 6:28 ` Christoph Hellwig [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=20240219062841.GA4410@lst.de \
--to=hch@lst.de \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).