Re: [PATCH -next v5 18/32] ext4: implement partial block zero range path using iomap
| Newsgroups | org.kernel.vger.linux-ext4 |
|---|---|
| Message-ID | <[email protected]> |
> From: Zhang Yi <[email protected]> > > Introduce a new iomap_ops instance, ext4_iomap_zero_ops, along with > ext4_iomap_block_zero_range() to implement block zeroing via the iomap > infrastructure for ext4. > > ext4_iomap_block_zero_range() calls iomap_zero_range() with > ext4_iomap_zero_begin() as the callback. The callback locates the > range and populates the iomap mapping. If the range is mapped, > iomap_zero_iter() in the iomap core zeros the partial block > directly. If the range is an unwritten extent within EOF, the > callback collects a dirty folio batch via iomap_fill_dirty_folios() > so that iomap_zero_iter() can zero those folios directly, bypassing > a separate slow flush operation that would otherwise be needed to > convert the unwritten extent. > [ ... ] > > Subsequent patches will address this by deferring i_disksize update > to i_size until after the zeroed data has been written back. > > Signed-off-by: Zhang Yi <[email protected]> Sashiko has reviewed this patch and found no issues. It looks great! -- Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=18