Hi all, Here's a bit more fallout and prep. work associated with the folio batch prototype posted a while back [1]. Work on that is still pending so it isn't included here, but based on the iter advance cleanups most of these seemed worthwhile as standalone cleanups. Mainly this just cleans up some of the helpers and pushes some pos/len trimming further down in the write begin path. The fbatch thing is still in prototype stage, but for context the intent here is that it can mostly now just bolt onto the folio lookup path because we can advance the range that is skipped and return the next folio along with the folio subrange for the caller to process. Thoughts, reviews, flames appreciated. Brian [1] https://lore.kernel.org/linux-fsdevel/20241213150528.1003662-1-bfoster@xxxxxxxxxx/ v2: - Split up warning in trim folio range helper. - Use min() and min_not_zero() instead of open coding. - Drop pos param from __iomap_write_begin() (folded into patch 6). v1: https://lore.kernel.org/linux-fsdevel/20250430190112.690800-1-bfoster@xxxxxxxxxx/ Brian Foster (6): iomap: resample iter->pos after iomap_write_begin() calls iomap: drop unnecessary pos param from iomap_write_[begin|end] iomap: drop pos param from __iomap_[get|put]_folio() iomap: helper to trim pos/bytes to within folio iomap: push non-large folio check into get folio path iomap: rework iomap_write_begin() to return folio offset and length fs/iomap/buffered-io.c | 100 ++++++++++++++++++++++++----------------- 1 file changed, 58 insertions(+), 42 deletions(-) -- 2.49.0
