Hi all, 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. It would be very useful if we could begin to tackle these problems by sharding the realtime section, so create the notion of realtime groups, which are similar to allocation groups on the data section. While we're at it, define a superblock to be stamped into the start of each rt section. This enables utilities such as blkid to identify block devices containing realtime sections, and helpfully avoids the situation where a file extent can cross an rtgroup boundary. 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. If you're going to start using this mess, you probably ought to just pull from my git trees, which are linked below. This is an extraordinary way to destroy everything. Enjoy! Comments and questions are, as always, welcome. --D kernel git tree: https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=realtime-groups xfsprogs git tree: https://git.kernel.org/cgit/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=realtime-groups fstests git tree: https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=realtime-groups --- common/fuzzy | 33 +++++++++++++++---- common/populate | 12 ++++++- common/xfs | 83 ++++++++++++++++++++++++++++++++++++++++------- src/punch-alternating.c | 28 +++++++++++++++- tests/xfs/114 | 4 ++ tests/xfs/122 | 2 + tests/xfs/122.out | 8 +++++ tests/xfs/146 | 2 + tests/xfs/185 | 2 + tests/xfs/187 | 3 +- tests/xfs/206 | 3 +- tests/xfs/271 | 3 +- tests/xfs/341 | 4 +- tests/xfs/449 | 6 +++ tests/xfs/556 | 16 ++++++--- tests/xfs/800 | 2 + tests/xfs/840 | 2 + tests/xfs/841 | 2 + 18 files changed, 176 insertions(+), 39 deletions(-)
