summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/mem-phys-addr.py
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2024-11-04 07:19:16 +0300
committerDarrick J. Wong <djwong@kernel.org>2024-11-06 00:38:39 +0300
commit64c58d7c99343a910edf995e15d8037e19ec5777 (patch)
treeceb79e0a35a59b85d1eea45bf0ed79f90e1a311b /tools/perf/scripts/python/mem-phys-addr.py
parentdca94251f617942f05c7c6ff30a299f6b7dff770 (diff)
downloadlinux-64c58d7c99343a910edf995e15d8037e19ec5777.tar.xz
iomap: add a merge boundary flag
File systems might have boundaries over which merges aren't possible. In fact these are very common, although most of the time some kind of header at the beginning of this region (e.g. XFS alloation groups, ext4 block groups) automatically create a merge barrier. But if that is not present, say for a device purely used for data we need to manually communicate that to iomap. Add a IOMAP_F_BOUNDARY flag to never merge I/O into a previous mapping. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions