Hi folks, As I play with the allocation of the metadata for the FLEX_BG feature, it seems that we could benefit from having block groups with no inode tables. Right now we allocate one inode table per bg base on the inode_blocks_per_group. For FLEX_BG though, it would make more sense to have a larger inode tables that fully use the inode bitmap allocated on the first few block groups. Once we reach the number of inode per FLEX_BG, then the remaining block groups could then have no inode tables defined. The idea here is that we better utilize the inode bitmaps and reduce the number of inode tables to improve mkfs/fsck times. We could also support expansion of inode since we have block groups that have empty entries in the block group descriptors and as long as we can find enough empty blocks for the inode table expanding the number of inodes should be relatively easy. Don't know if ext4 currently supports this. Any thoughts? -JRS - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
