diff options
| author | Brian Foster <bfoster@redhat.com> | 2026-03-11 12:25:01 -0400 |
|---|---|---|
| committer | Carlos Maiolino <cem@kernel.org> | 2026-03-23 11:07:59 +0100 |
| commit | ce9d27ca8b2eafdd2457a15aafdab74218843138 (patch) | |
| tree | 0ca310986f359764aae9e05813068b3271262f21 /tools/perf/scripts/python/stackcollapse.py | |
| parent | c770f997a4227b6fc5f62275b2337622213e35af (diff) | |
xfs: replace zero range flush with folio batch
Now that the zero range pagecache flush is purely isolated to
providing zeroing correctness in this case, we can remove it and
replace it with the folio batch mechanism that is used for handling
unwritten extents.
This is still slightly odd in that XFS reports a hole vs. a mapping
that reflects the COW fork extents, but that has always been the
case in this situation and so a separate issue. We drop the iomap
warning that assumes the folio batch is always associated with
unwritten mappings, but this is mainly a development assertion as
otherwise the core iomap fbatch code doesn't care much about the
mapping type if it's handed the set of folios to process.
Signed-off-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
