summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/mem-phys-addr.py
diff options
context:
space:
mode:
authorCarlos Maiolino <cem@kernel.org>2024-11-12 13:00:42 +0300
committerCarlos Maiolino <cem@kernel.org>2024-11-12 13:00:42 +0300
commitb939bcdca3756db877aa084edd70901624faf26a (patch)
tree89e070904515052ed6741928bf6626e8c3b60fce /tools/perf/scripts/python/mem-phys-addr.py
parentcb288c9fb2aba9a5d71b8191dfcb6f2cced37f7a (diff)
parenta3315d11305f5c2d82fcb00e3df34775adff4084 (diff)
downloadlinux-b939bcdca3756db877aa084edd70901624faf26a.tar.xz
Merge tag 'realtime-groups-6.13_2024-11-05' of https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux into staging-merge
xfs: shard the realtime section [v5.5 06/10] Right now, the realtime section uses a single pair of metadata inodes to store the free space information. This presents a scalability problem since every thread trying to allocate or free rt extents have to lock these files. Solve this problem by sharding the realtime section into separate realtime allocation groups. While we're at it, define a superblock to be stamped into the start of the rt section. This enables utilities such as blkid to identify block devices containing realtime sections, and avoids the situation where anything written into block 0 of the realtime extent can be misinterpreted as file data. The best advantage for rtgroups will become evident later when we get to adding rmap and reflink to the realtime volume, since the geometry constraints are the same for rt groups and AGs. Hence we can reuse all that code directly. This is a very large patchset, but it catches us up with 20 years of technical debt that have accumulated. With a bit of luck, this should all go splendidly. 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