From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-mm@kvack.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Jan Kara <jack@suse.com>, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 03/11] writeback: Factor should_writeback_folio() out of write_cache_pages()
Date: Fri, 15 Dec 2023 15:16:31 +0100 [thread overview]
Message-ID: <20231215141631.aooan5rby6fwfdof@quack3> (raw)
In-Reply-To: <20231214132544.376574-4-hch@lst.de>
On Thu 14-12-23 14:25:36, Christoph Hellwig wrote:
> From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
>
> Reduce write_cache_pages() by about 30 lines; much of it is commentary,
> but it all bundles nicely into an obvious function.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
I like this! Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> mm/page-writeback.c | 59 ++++++++++++++++++++++++---------------------
> 1 file changed, 32 insertions(+), 27 deletions(-)
>
> diff --git a/mm/page-writeback.c b/mm/page-writeback.c
> index 5d33e7b468e2cc..5a3df8665ff4f9 100644
> --- a/mm/page-writeback.c
> +++ b/mm/page-writeback.c
> @@ -2394,6 +2394,36 @@ static void writeback_get_batch(struct address_space *mapping,
> &wbc->fbatch);
> }
>
> +static bool should_writeback_folio(struct address_space *mapping,
> + struct writeback_control *wbc, struct folio *folio)
> +{
> + /*
> + * Folio truncated or invalidated. We can freely skip it then,
> + * even for data integrity operations: the folio has disappeared
> + * concurrently, so there could be no real expectation of this
> + * data integrity operation even if there is now a new, dirty
> + * folio at the same pagecache index.
> + */
> + if (unlikely(folio->mapping != mapping))
> + return false;
> +
> + /* Did somebody write it for us? */
> + if (!folio_test_dirty(folio))
> + return false;
> +
> + if (folio_test_writeback(folio)) {
> + if (wbc->sync_mode == WB_SYNC_NONE)
> + return false;
> + folio_wait_writeback(folio);
> + }
> +
> + BUG_ON(folio_test_writeback(folio));
> + if (!folio_clear_dirty_for_io(folio))
> + return false;
> +
> + return true;
> +}
> +
> /**
> * write_cache_pages - walk the list of dirty pages of the given address space and write all of them.
> * @mapping: address space structure to write
> @@ -2462,38 +2492,13 @@ int write_cache_pages(struct address_space *mapping,
> wbc->done_index = folio->index;
>
> folio_lock(folio);
> -
> - /*
> - * Page truncated or invalidated. We can freely skip it
> - * then, even for data integrity operations: the page
> - * has disappeared concurrently, so there could be no
> - * real expectation of this data integrity operation
> - * even if there is now a new, dirty page at the same
> - * pagecache address.
> - */
> - if (unlikely(folio->mapping != mapping)) {
> -continue_unlock:
> + if (!should_writeback_folio(mapping, wbc, folio)) {
> folio_unlock(folio);
> continue;
> }
>
> - if (!folio_test_dirty(folio)) {
> - /* someone wrote it for us */
> - goto continue_unlock;
> - }
> -
> - if (folio_test_writeback(folio)) {
> - if (wbc->sync_mode != WB_SYNC_NONE)
> - folio_wait_writeback(folio);
> - else
> - goto continue_unlock;
> - }
> -
> - BUG_ON(folio_test_writeback(folio));
> - if (!folio_clear_dirty_for_io(folio))
> - goto continue_unlock;
> -
> trace_wbc_writepage(wbc, inode_to_bdi(mapping->host));
> +
> error = writepage(folio, wbc, data);
> nr = folio_nr_pages(folio);
> if (unlikely(error)) {
> --
> 2.39.2
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-12-15 14:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 13:25 Convert write_cache_pages() to an iterator v2 Christoph Hellwig
2023-12-14 13:25 ` [PATCH 01/11] writeback: Factor out writeback_finish() Christoph Hellwig
2023-12-15 13:26 ` Jan Kara
2023-12-15 16:54 ` Christoph Hellwig
2023-12-14 13:25 ` [PATCH 02/11] writeback: Factor writeback_get_batch() out of write_cache_pages() Christoph Hellwig
2023-12-15 14:14 ` Jan Kara
2023-12-14 13:25 ` [PATCH 03/11] writeback: Factor should_writeback_folio() " Christoph Hellwig
2023-12-15 14:16 ` Jan Kara [this message]
2023-12-14 13:25 ` [PATCH 04/11] writeback: Simplify the loops in write_cache_pages() Christoph Hellwig
2023-12-15 14:25 ` Jan Kara
2023-12-16 6:16 ` Matthew Wilcox
2023-12-14 13:25 ` [PATCH 05/11] pagevec: Add ability to iterate a queue Christoph Hellwig
2023-12-14 13:25 ` [PATCH 06/11] writeback: Use the folio_batch queue iterator Christoph Hellwig
2023-12-14 13:25 ` [PATCH 07/11] writeback: Factor writeback_iter_init() out of write_cache_pages() Christoph Hellwig
2023-12-14 13:25 ` [PATCH 08/11] writeback: Factor writeback_get_folio() " Christoph Hellwig
2023-12-14 13:25 ` [PATCH 09/11] writeback: Factor writeback_iter_next() " Christoph Hellwig
2023-12-15 14:17 ` Brian Foster
2023-12-16 4:51 ` Christoph Hellwig
2023-12-14 13:25 ` [PATCH 10/11] writeback: Add for_each_writeback_folio() Christoph Hellwig
2023-12-14 13:25 ` [PATCH 11/11] writeback: Remove a use of write_cache_pages() from do_writepages() 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=20231215141631.aooan5rby6fwfdof@quack3 \
--to=jack@suse.cz \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--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