From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Brauner <brauner@kernel.org>,
Chandan Babu R <chandan.babu@oracle.com>,
Zhang Yi <yi.zhang@huaweicloud.com>,
Ritesh Harjani <ritesh.list@gmail.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 11/13] iomap: factor out a iomap_writepage_map_block helper
Date: Tue, 28 Nov 2023 21:06:42 -0800 [thread overview]
Message-ID: <20231129050642.GQ4167244@frogsfrogsfrogs> (raw)
In-Reply-To: <20231126124720.1249310-12-hch@lst.de>
On Sun, Nov 26, 2023 at 01:47:18PM +0100, Christoph Hellwig wrote:
> Split the loop body that calls into the file system to map a block and
> add it to the ioend into a separate helper to prefer for refactoring of
> the surrounding code.
>
> Note that this was the only place in iomap_writepage_map that could
> return an error, so include the call to ->discard_folio into the new
> helper as that will help to avoid code duplication in the future.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Simple enough hoist,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/iomap/buffered-io.c | 72 +++++++++++++++++++++++++-----------------
> 1 file changed, 43 insertions(+), 29 deletions(-)
>
> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> index e1d5076251702d..9f223820f60d22 100644
> --- a/fs/iomap/buffered-io.c
> +++ b/fs/iomap/buffered-io.c
> @@ -1723,6 +1723,45 @@ static void iomap_add_to_ioend(struct iomap_writepage_ctx *wpc,
> wbc_account_cgroup_owner(wbc, &folio->page, len);
> }
>
> +static int iomap_writepage_map_blocks(struct iomap_writepage_ctx *wpc,
> + struct writeback_control *wbc, struct folio *folio,
> + struct inode *inode, u64 pos, unsigned *count,
> + struct list_head *submit_list)
> +{
> + int error;
> +
> + error = wpc->ops->map_blocks(wpc, inode, pos);
> + if (error)
> + goto fail;
> + trace_iomap_writepage_map(inode, &wpc->iomap);
> +
> + switch (wpc->iomap.type) {
> + case IOMAP_INLINE:
> + WARN_ON_ONCE(1);
> + error = -EIO;
> + break;
> + case IOMAP_HOLE:
> + break;
> + default:
> + iomap_add_to_ioend(wpc, wbc, folio, inode, pos, submit_list);
> + (*count)++;
> + }
> +
> +fail:
> + /*
> + * We cannot cancel the ioend directly here on error. We may have
> + * already set other pages under writeback and hence we have to run I/O
> + * completion to mark the error state of the pages under writeback
> + * appropriately.
> + *
> + * Just let the file system know what portion of the folio failed to
> + * map.
> + */
> + if (error && wpc->ops->discard_folio)
> + wpc->ops->discard_folio(folio, pos);
> + return error;
> +}
> +
> /*
> * Check interaction of the folio with the file end.
> *
> @@ -1807,7 +1846,8 @@ static int iomap_writepage_map(struct iomap_writepage_ctx *wpc,
> unsigned nblocks = i_blocks_per_folio(inode, folio);
> u64 pos = folio_pos(folio);
> u64 end_pos = pos + folio_size(folio);
> - int error = 0, count = 0, i;
> + unsigned count = 0;
> + int error = 0, i;
> LIST_HEAD(submit_list);
>
> trace_iomap_writepage(inode, pos, folio_size(folio));
> @@ -1833,19 +1873,10 @@ static int iomap_writepage_map(struct iomap_writepage_ctx *wpc,
> for (i = 0; i < nblocks && pos < end_pos; i++, pos += len) {
> if (ifs && !ifs_block_is_dirty(folio, ifs, i))
> continue;
> -
> - error = wpc->ops->map_blocks(wpc, inode, pos);
> + error = iomap_writepage_map_blocks(wpc, wbc, folio, inode, pos,
> + &count, &submit_list);
> if (error)
> break;
> - trace_iomap_writepage_map(inode, &wpc->iomap);
> - if (WARN_ON_ONCE(wpc->iomap.type == IOMAP_INLINE)) {
> - error = -EIO;
> - break;
> - }
> - if (wpc->iomap.type == IOMAP_HOLE)
> - continue;
> - iomap_add_to_ioend(wpc, wbc, folio, inode, pos, &submit_list);
> - count++;
> }
> if (count)
> wpc->nr_folios++;
> @@ -1855,23 +1886,6 @@ static int iomap_writepage_map(struct iomap_writepage_ctx *wpc,
> WARN_ON_ONCE(folio_test_writeback(folio));
> WARN_ON_ONCE(folio_test_dirty(folio));
>
> - /*
> - * We cannot cancel the ioend directly here on error. We may have
> - * already set other pages under writeback and hence we have to run I/O
> - * completion to mark the error state of the pages under writeback
> - * appropriately.
> - */
> - if (unlikely(error)) {
> - /*
> - * Let the filesystem know what portion of the current page
> - * failed to map. If the page hasn't been added to ioend, it
> - * won't be affected by I/O completion and we must unlock it
> - * now.
> - */
> - if (wpc->ops->discard_folio)
> - wpc->ops->discard_folio(folio, pos);
> - }
> -
> /*
> * We can have dirty bits set past end of file in page_mkwrite path
> * while mapping the last partial folio. Hence it's better to clear
> --
> 2.39.2
>
>
next prev parent reply other threads:[~2023-11-29 5:06 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 12:47 RFC: map multiple blocks per ->map_blocks in iomap writeback Christoph Hellwig
2023-11-26 12:47 ` [PATCH 01/13] iomap: clear the per-folio dirty bits on all writeback failures Christoph Hellwig
2023-11-27 3:47 ` Ritesh Harjani
2023-11-27 6:29 ` Christoph Hellwig
2023-11-26 12:47 ` [PATCH 02/13] iomap: treat inline data in iomap_writepage_map as an I/O error Christoph Hellwig
2023-11-27 5:01 ` Ritesh Harjani
2023-11-27 6:33 ` Christoph Hellwig
2023-11-29 4:40 ` Darrick J. Wong
2023-11-29 5:39 ` Christoph Hellwig
2023-11-26 12:47 ` [PATCH 03/13] iomap: move the io_folios field out of struct iomap_ioend Christoph Hellwig
2023-11-27 5:33 ` Ritesh Harjani
2023-11-29 4:41 ` Darrick J. Wong
2023-11-26 12:47 ` [PATCH 04/13] iomap: drop the obsolete PF_MEMALLOC check in iomap_do_writepage Christoph Hellwig
2023-11-27 6:39 ` Ritesh Harjani
2023-11-27 6:41 ` Christoph Hellwig
2023-11-29 4:45 ` Darrick J. Wong
2023-11-26 12:47 ` [PATCH 05/13] iomap: factor out a iomap_writepage_handle_eof helper Christoph Hellwig
2023-11-27 6:57 ` Ritesh Harjani
2023-11-27 7:02 ` Ritesh Harjani
2023-11-27 7:12 ` Christoph Hellwig
2023-11-29 4:48 ` Darrick J. Wong
2023-11-26 12:47 ` [PATCH 06/13] iomap: move all remaining per-folio logic into xfs_writepage_map Christoph Hellwig
2023-11-27 7:36 ` Ritesh Harjani
2023-11-27 19:20 ` Josef Bacik
2023-11-29 4:50 ` Darrick J. Wong
2023-11-26 12:47 ` [PATCH 07/13] iomap: clean up the iomap_new_ioend calling convention Christoph Hellwig
2023-11-27 7:43 ` Ritesh Harjani
2023-11-27 8:13 ` Christoph Hellwig
2023-11-29 4:51 ` Darrick J. Wong
2023-11-26 12:47 ` [PATCH 08/13] iomap: move the iomap_sector sector calculation out of iomap_add_to_ioend Christoph Hellwig
2023-11-27 9:54 ` Ritesh Harjani
2023-11-27 13:54 ` Christoph Hellwig
2023-11-29 4:53 ` Darrick J. Wong
2023-11-29 5:42 ` Christoph Hellwig
2023-11-26 12:47 ` [PATCH 09/13] iomap: don't chain bios Christoph Hellwig
2023-11-27 12:53 ` Zhang Yi
2023-11-27 13:51 ` Christoph Hellwig
2023-11-29 4:59 ` Darrick J. Wong
2023-11-29 5:40 ` Christoph Hellwig
2023-11-26 12:47 ` [PATCH 10/13] iomap: only call mapping_set_error once for each failed bio Christoph Hellwig
2023-11-29 5:03 ` Darrick J. Wong
2023-11-29 5:41 ` Christoph Hellwig
2023-11-26 12:47 ` [PATCH 11/13] iomap: factor out a iomap_writepage_map_block helper Christoph Hellwig
2023-11-29 5:06 ` Darrick J. Wong [this message]
2023-11-26 12:47 ` [PATCH 12/13] iomap: submit ioends immediately Christoph Hellwig
2023-11-29 5:14 ` Darrick J. Wong
2023-11-26 12:47 ` [PATCH 13/13] iomap: map multiple blocks at a time Christoph Hellwig
2023-11-29 5:25 ` Darrick J. Wong
2023-11-29 5:44 ` 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=20231129050642.GQ4167244@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=yi.zhang@huaweicloud.com \
/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).