From: "Darrick J. Wong" <djwong@kernel.org>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v5 10/10] iomap: advance the iter directly on zero range
Date: Wed, 5 Feb 2025 11:15:03 -0800 [thread overview]
Message-ID: <20250205191503.GR21808@frogsfrogsfrogs> (raw)
In-Reply-To: <20250205135821.178256-11-bfoster@redhat.com>
On Wed, Feb 05, 2025 at 08:58:21AM -0500, Brian Foster wrote:
> Modify zero range to advance the iter directly. Replace the local pos
> and length calculations with direct advances and loop based on iter
> state instead.
>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/iomap/buffered-io.c | 24 +++++++++++++-----------
> 1 file changed, 13 insertions(+), 11 deletions(-)
>
> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> index f953bf66beb1..ec227b45f3aa 100644
> --- a/fs/iomap/buffered-io.c
> +++ b/fs/iomap/buffered-io.c
> @@ -1345,17 +1345,16 @@ static inline int iomap_zero_iter_flush_and_stale(struct iomap_iter *i)
>
> static loff_t iomap_zero_iter(struct iomap_iter *iter, bool *did_zero)
> {
> - loff_t pos = iter->pos;
> - loff_t length = iomap_length(iter);
> - loff_t written = 0;
> + u64 bytes = iomap_length(iter);
> + int status;
>
> do {
> struct folio *folio;
> - int status;
> size_t offset;
> - size_t bytes = min_t(u64, SIZE_MAX, length);
> + loff_t pos = iter->pos;
I wonder, is there any need for the local variable here?
Looks fine to me though.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> bool ret;
>
> + bytes = min_t(u64, SIZE_MAX, bytes);
> status = iomap_write_begin(iter, pos, bytes, &folio);
> if (status)
> return status;
> @@ -1376,14 +1375,14 @@ static loff_t iomap_zero_iter(struct iomap_iter *iter, bool *did_zero)
> if (WARN_ON_ONCE(!ret))
> return -EIO;
>
> - pos += bytes;
> - length -= bytes;
> - written += bytes;
> - } while (length > 0);
> + status = iomap_iter_advance(iter, &bytes);
> + if (status)
> + break;
> + } while (bytes > 0);
>
> if (did_zero)
> *did_zero = true;
> - return written;
> + return status;
> }
>
> int
> @@ -1436,11 +1435,14 @@ iomap_zero_range(struct inode *inode, loff_t pos, loff_t len, bool *did_zero,
>
> if (srcmap->type == IOMAP_HOLE ||
> srcmap->type == IOMAP_UNWRITTEN) {
> - loff_t proc = iomap_length(&iter);
> + s64 proc;
>
> if (range_dirty) {
> range_dirty = false;
> proc = iomap_zero_iter_flush_and_stale(&iter);
> + } else {
> + u64 length = iomap_length(&iter);
> + proc = iomap_iter_advance(&iter, &length);
> }
> iter.processed = proc;
> continue;
> --
> 2.48.1
>
>
prev parent reply other threads:[~2025-02-05 19:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 13:58 [PATCH v5 00/10] iomap: incremental per-operation iter advance Brian Foster
2025-02-05 13:58 ` [PATCH v5 01/10] iomap: factor out iomap length helper Brian Foster
2025-02-05 18:49 ` Darrick J. Wong
2025-02-05 13:58 ` [PATCH v5 02/10] iomap: split out iomap check and reset logic from iter advance Brian Foster
2025-02-05 13:58 ` [PATCH v5 03/10] iomap: refactor iomap_iter() length check and tracepoint Brian Foster
2025-02-05 18:50 ` Darrick J. Wong
2025-02-05 13:58 ` [PATCH v5 04/10] iomap: lift error code check out of iomap_iter_advance() Brian Foster
2025-02-05 18:51 ` Darrick J. Wong
2025-02-05 13:58 ` [PATCH v5 05/10] iomap: lift iter termination logic from iomap_iter_advance() Brian Foster
2025-02-05 19:00 ` Darrick J. Wong
2025-02-05 20:25 ` Brian Foster
2025-02-05 13:58 ` [PATCH v5 06/10] iomap: export iomap_iter_advance() and return remaining length Brian Foster
2025-02-05 18:58 ` Darrick J. Wong
2025-02-05 20:25 ` Brian Foster
2025-02-05 13:58 ` [PATCH v5 07/10] iomap: support incremental iomap_iter advances Brian Foster
2025-02-05 19:10 ` Darrick J. Wong
2025-02-05 20:26 ` Brian Foster
2025-02-05 13:58 ` [PATCH v5 08/10] iomap: advance the iter directly on buffered writes Brian Foster
2025-02-05 19:17 ` Darrick J. Wong
2025-02-05 13:58 ` [PATCH v5 09/10] iomap: advance the iter directly on unshare range Brian Foster
2025-02-05 19:16 ` Darrick J. Wong
2025-02-05 20:27 ` Brian Foster
2025-02-05 20:44 ` Darrick J. Wong
2025-02-05 13:58 ` [PATCH v5 10/10] iomap: advance the iter directly on zero range Brian Foster
2025-02-05 19:15 ` Darrick J. Wong [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=20250205191503.GR21808@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).