From: Brian Foster <bfoster@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-xfs@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: [PATCH v3 3/7] iomap: refactor iter and advance continuation logic
Date: Thu, 30 Jan 2025 12:09:44 -0500 [thread overview]
Message-ID: <20250130170949.916098-4-bfoster@redhat.com> (raw)
In-Reply-To: <20250130170949.916098-1-bfoster@redhat.com>
In preparation for future changes and more generic use of
iomap_iter_advance(), lift the high level iter continuation logic
out of iomap_iter_advance() into the caller. Also add some comments
and rework iomap_iter() to jump straight to ->iomap_begin() on the
first iteration.
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
fs/iomap/iter.c | 66 ++++++++++++++++++++++++-------------------
include/linux/iomap.h | 1 +
2 files changed, 38 insertions(+), 29 deletions(-)
diff --git a/fs/iomap/iter.c b/fs/iomap/iter.c
index 731ea7267f27..0a13d50e9ffd 100644
--- a/fs/iomap/iter.c
+++ b/fs/iomap/iter.c
@@ -15,31 +15,17 @@ static inline void iomap_iter_reset_iomap(struct iomap_iter *iter)
}
/*
- * Advance to the next range we need to map.
- *
- * If the iomap is marked IOMAP_F_STALE, it means the existing map was not fully
- * processed - it was aborted because the extent the iomap spanned may have been
- * changed during the operation. In this case, the iteration behaviour is to
- * remap the unprocessed range of the iter, and that means we may need to remap
- * even when we've made no progress (i.e. count = 0). Hence the "finished
- * iterating" case needs to distinguish between (count = 0) meaning we are done
- * and (count = 0 && stale) meaning we need to remap the entire remaining range.
+ * Advance the current iterator position and return the length remaining for the
+ * current mapping.
*/
-static inline int iomap_iter_advance(struct iomap_iter *iter, s64 count)
+int iomap_iter_advance(struct iomap_iter *iter, u64 *count)
{
- bool stale = iter->iomap.flags & IOMAP_F_STALE;
- int ret = 1;
-
- if (count < 0)
- return count;
- if (WARN_ON_ONCE(count > iomap_length(iter)))
+ if (WARN_ON_ONCE(*count > iomap_length(iter)))
return -EIO;
- iter->pos += count;
- iter->len -= count;
- if (!iter->len || (!count && !stale))
- ret = 0;
-
- return ret;
+ iter->pos += *count;
+ iter->len -= *count;
+ *count = iomap_length(iter);
+ return 0;
}
static inline void iomap_iter_done(struct iomap_iter *iter)
@@ -71,9 +57,16 @@ static inline void iomap_iter_done(struct iomap_iter *iter)
*/
int iomap_iter(struct iomap_iter *iter, const struct iomap_ops *ops)
{
+ bool stale = iter->iomap.flags & IOMAP_F_STALE;
+ s64 processed;
int ret;
- if (iter->iomap.length && ops->iomap_end) {
+ trace_iomap_iter(iter, ops, _RET_IP_);
+
+ if (!iter->iomap.length)
+ goto begin;
+
+ if (ops->iomap_end) {
ret = ops->iomap_end(iter->inode, iter->pos, iomap_length(iter),
iter->processed > 0 ? iter->processed : 0,
iter->flags, &iter->iomap);
@@ -81,15 +74,30 @@ int iomap_iter(struct iomap_iter *iter, const struct iomap_ops *ops)
return ret;
}
- /* advance and clear state from the previous iteration */
- trace_iomap_iter(iter, ops, _RET_IP_);
- if (iter->iomap.length) {
- ret = iomap_iter_advance(iter, iter->processed);
+ processed = iter->processed;
+ if (processed < 0) {
iomap_iter_reset_iomap(iter);
- if (ret <= 0)
- return ret;
+ return processed;
}
+ /*
+ * Advance the iter and clear state from the previous iteration. The
+ * remaining length of the previous iteration should be zero by this
+ * point, so use iter->len to determine whether to continue onto the
+ * next mapping. Explicitly terminate in the case where the current iter
+ * has not advanced at all (i.e. no work was done for some reason)
+ * unless the mapping has been marked stale and needs to be reprocessed.
+ */
+ ret = iomap_iter_advance(iter, &processed);
+ if (!ret && iter->len > 0)
+ ret = 1;
+ if (ret > 0 && !iter->processed && !stale)
+ ret = 0;
+ iomap_iter_reset_iomap(iter);
+ if (ret <= 0)
+ return ret;
+
+begin:
ret = ops->iomap_begin(iter->inode, iter->pos, iter->len, iter->flags,
&iter->iomap, &iter->srcmap);
if (ret < 0)
diff --git a/include/linux/iomap.h b/include/linux/iomap.h
index f5ca71ac2fa2..f304c602e5fe 100644
--- a/include/linux/iomap.h
+++ b/include/linux/iomap.h
@@ -229,6 +229,7 @@ struct iomap_iter {
};
int iomap_iter(struct iomap_iter *iter, const struct iomap_ops *ops);
+int iomap_iter_advance(struct iomap_iter *iter, u64 *count);
/**
* iomap_length_trim - trimmed length of the current iomap iteration
--
2.47.1
next prev parent reply other threads:[~2025-01-30 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 17:09 [PATCH v3 0/7] iomap: incremental per-operation iter advance Brian Foster
2025-01-30 17:09 ` [PATCH v3 1/7] iomap: split out iomap check and reset logic from " Brian Foster
2025-01-30 17:09 ` [PATCH v3 2/7] iomap: factor out iomap length helper Brian Foster
2025-01-30 17:09 ` Brian Foster [this message]
2025-01-31 8:08 ` [PATCH v3 3/7] iomap: refactor iter and advance continuation logic Christoph Hellwig
2025-01-31 12:50 ` Brian Foster
2025-01-30 17:09 ` [PATCH v3 4/7] iomap: support incremental iomap_iter advances Brian Foster
2025-01-30 17:09 ` [PATCH v3 5/7] iomap: advance the iter directly on buffered writes Brian Foster
2025-01-30 17:09 ` [PATCH v3 6/7] iomap: advance the iter directly on unshare range Brian Foster
2025-01-31 8:09 ` Christoph Hellwig
2025-01-30 17:09 ` [PATCH v3 7/7] iomap: advance the iter directly on zero range Brian Foster
2025-01-31 8:09 ` 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=20250130170949.916098-4-bfoster@redhat.com \
--to=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