Executive summary of the day's work: Yesterday morning: 944 bytes per inode in core Yesterday night: 24 bytes per inode in core Tonight: 4 bytes per inode in core. That's a x236 time reduction in memory usage. No I didn't even start looking at a freezer. Which could bring that 4 down to 0, but would add a scalability penalty on all inodes when IMA was enabled. The memory associated with inodes that IMA actually cares about has gone from 312 to 320 bytes. I'm going to follow up with my patch series again but they aren't really ready to be applied. The IBM people who wrote IMA are reviewing them. I have some questions if my RCU+RBTREE usage is valid/correct. I'd really like Al to take a close look at the last patch in the series to make sure my use of i_writecount actually does what I want it to do... -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
