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 v4 00/10] iomap: incremental per-operation iter advance
Date: Tue, 4 Feb 2025 08:30:34 -0500 [thread overview]
Message-ID: <20250204133044.80551-1-bfoster@redhat.com> (raw)
Hi all,
Here's v4 of the incremental advance series. No major changes here.. a
couple patches have been reordered in the series and patch 3 in v3 has
been split up into several smaller patches.
Thoughts, reviews, flames appreciated.
Brian
v4:
- Reordered patches 1 and 2 to keep iter advance cleanups together.
- Split patch 3 from v3 into patches 3-6.
v3: https://lore.kernel.org/linux-fsdevel/20250130170949.916098-1-bfoster@redhat.com/
- Code style and comment fixups.
- Variable type fixups and rework of iomap_iter_advance() to return
error/length separately.
- Advance the iter on unshare and zero range skip cases instead of
returning length.
v2: https://lore.kernel.org/linux-fsdevel/20250122133434.535192-1-bfoster@redhat.com/
- More refactoring of iomap_iter[_advance]() logic. Lifted out iter
continuation and stale logic and improved comments.
- Renamed some poorly named helpers and variables.
- Return remaining length for current iter from _iter_advance() and use
appropriately.
v1: https://lore.kernel.org/linux-fsdevel/20241213143610.1002526-1-bfoster@redhat.com/
- Reworked and fixed a bunch of functional issues.
RFC: https://lore.kernel.org/linux-fsdevel/20241125140623.20633-1-bfoster@redhat.com/
Brian Foster (10):
iomap: factor out iomap length helper
iomap: split out iomap check and reset logic from iter advance
iomap: refactor iomap_iter() length check and tracepoint
iomap: lift error code check out of iomap_iter_advance()
iomap: lift iter termination logic from iomap_iter_advance()
iomap: export iomap_iter_advance() and return remaining length
iomap: support incremental iomap_iter advances
iomap: advance the iter directly on buffered writes
iomap: advance the iter directly on unshare range
iomap: advance the iter directly on zero range
fs/iomap/buffered-io.c | 67 +++++++++++++--------------
fs/iomap/iter.c | 102 ++++++++++++++++++++++++++---------------
include/linux/iomap.h | 27 +++++++++--
3 files changed, 119 insertions(+), 77 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-04 13:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 13:30 Brian Foster [this message]
2025-02-04 13:30 ` [PATCH v4 01/10] iomap: factor out iomap length helper Brian Foster
2025-02-04 13:30 ` [PATCH v4 02/10] iomap: split out iomap check and reset logic from iter advance Brian Foster
2025-02-04 19:30 ` Darrick J. Wong
2025-02-04 19:48 ` Brian Foster
2025-02-04 13:30 ` [PATCH v4 03/10] iomap: refactor iomap_iter() length check and tracepoint Brian Foster
2025-02-04 13:50 ` Christoph Hellwig
2025-02-04 13:30 ` [PATCH v4 04/10] iomap: lift error code check out of iomap_iter_advance() Brian Foster
2025-02-04 13:51 ` Christoph Hellwig
2025-02-04 19:23 ` Darrick J. Wong
2025-02-04 19:48 ` Brian Foster
2025-02-04 13:30 ` [PATCH v4 05/10] iomap: lift iter termination logic from iomap_iter_advance() Brian Foster
2025-02-04 13:51 ` Christoph Hellwig
2025-02-04 19:52 ` Darrick J. Wong
2025-02-04 20:15 ` Brian Foster
2025-02-04 13:30 ` [PATCH v4 06/10] iomap: export iomap_iter_advance() and return remaining length Brian Foster
2025-02-04 13:52 ` Christoph Hellwig
2025-02-04 13:30 ` [PATCH v4 07/10] iomap: support incremental iomap_iter advances Brian Foster
2025-02-04 13:30 ` [PATCH v4 08/10] iomap: advance the iter directly on buffered writes Brian Foster
2025-02-04 13:30 ` [PATCH v4 09/10] iomap: advance the iter directly on unshare range Brian Foster
2025-02-04 13:30 ` [PATCH v4 10/10] iomap: advance the iter directly on zero range Brian Foster
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=20250204133044.80551-1-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.