The advantage of having two structs means that both struct inode and the
private info can be aligned nicely. Yes it potentially wastes a tiny
bit more memory, but I challenge you to find an architecture where doing
this isn't a win. In a couple cases I looked at, additional slabs are
not even necessary, as kmalloc's standard ones do the job quite well.
'cat /proc/slabinfo' for a list of the sizes.
Note this only applies to inodes. There aren't enough superblocks in a
running system to worry about doing anything but simple kmalloc on the
superblock private info (before assigning to generic_sbp).
Jeff
-- Jeff Garzik | Only so many songs can be sung Building 1024 | with two lips, two lungs, and one tongue. MandrakeSoft | - nomeansno- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/