diff options
| author | Darrick J. Wong <djwong@kernel.org> | 2024-11-04 07:19:16 +0300 |
|---|---|---|
| committer | Darrick J. Wong <djwong@kernel.org> | 2024-11-06 00:38:38 +0300 |
| commit | dca94251f617942f05c7c6ff30a299f6b7dff770 (patch) | |
| tree | 2be107d46a9d016426de504e2eb378c616357de9 /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | f220f6da5f4ad7da538c39075cf57e829d5202f7 (diff) | |
| download | linux-dca94251f617942f05c7c6ff30a299f6b7dff770.tar.xz | |
xfs: fix rt device offset calculations for FITRIM
FITRIM on xfs has this bizarro uapi where we flatten all the physically
addressable storage across two block devices into a linear address
space. In this address space, the realtime device comes immediately
after the data device. Therefore, the xfs_trim_rtdev_extents has to
convert its input parameters from the linear address space to actual
rtdev block addresses on the realtime volume.
Right now the address space conversion is done in units of rtblocks.
However, a future patchset will convert xfs_rtblock_t to be a segmented
address space (group:blkno) like the data device. Change the conversion
code to be done in units of daddrs since those will never be segmented.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions