On Wed, 16 Jul 2025 14:54:01 +0200, Christoph Hellwig wrote:
> Busy extent tracking is primarily used to ensure that freed blocks are
> not reused for data allocations before the transaction that deleted them
> has been committed to stable storage, and secondarily to drive online
> discard. None of the use cases applies to zoned RTGs, as the zoned
> allocator can't overwrite blocks before resetting the zone, which already
> flushes out all transactions touching the RTGs.
>
> [...]
Applied to for-next, thanks!
[1/7] xfs: don't allocate the xfs_extent_busy structure for zoned RTGs
commit: 48510b0d85220f61337ad497dfc26ac2beb50413
[2/7] xfs: use a uint32_t to cache i_used_blocks in xfs_init_zone
commit: c11330b4ac1141ac6c3bfce93333405dc3bb5628
[3/7] xfs: rename oz_write_pointer to oz_allocated
commit: 8a034f984dfe32b4bf23d6729b04d37b14a76cbd
[4/7] xfs: stop passing an inode to the zone space reservation helpers
commit: 7a779c6867faf3e2e06e60d2774af648da468c7d
[5/7] xfs: replace min & max with clamp() in xfs_max_open_zones()
(no commit info)
[6/7] xfs: improve the comments in xfs_max_open_zones
commit: 8196283484ec758b067adb9405299da675e2411d
[7/7] xfs: improve the comments in xfs_select_zone_nowait
commit: e381d3e2c80d4b163302e53d0a0879c59ccff148
Best regards,
--
Carlos Maiolino <cem@xxxxxxxxxx>
