diff options
author | Christoph Hellwig <hch@lst.de> | 2025-08-18 08:06:43 +0300 |
---|---|---|
committer | Carlos Maiolino <cem@kernel.org> | 2025-08-19 15:37:07 +0300 |
commit | d004d70d6cdf03928da0d05c8c15c2ccc15657cd (patch) | |
tree | 88c726add4d170d5adf40fd9fc272386a331403d /tools/testing/selftests/bpf/prog_tests/prog_array_init.c | |
parent | 9ce43caa4b7be707638d49ad4fb358b6ff646e91 (diff) | |
download | linux-d004d70d6cdf03928da0d05c8c15c2ccc15657cd.tar.xz |
xfs: remove xfs_last_used_zone
This was my first attempt at caching the last used zone. But it turns out
for O_DIRECT or RWF_DONTCACHE that operate concurrently or in very short
sequence, the bmap btree does not record a written extent yet, so it fails.
Because it then still finds the last written zone it can lead to a weird
ping-pong around a few zones with writers seeing different values.
Remove it entirely as the later added xfs_cached_zone actually does a
much better job enforcing the locality as the zone is associated with the
inode in the MRU cache as soon as the zone is selected.
Fixes: 4e4d52075577 ("xfs: add the zoned space allocator")
Signed-off-by: Christoph Hellwig <hch@lst.de>
Tested-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Hans Holmberg <hans.holmberg@wdc.com>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/prog_array_init.c')
0 files changed, 0 insertions, 0 deletions