On Fri, Oct 08, 2010 at 04:21:16PM +1100, Dave Chinner wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > The number of inodes allocated does not need to be tied to the > addition or removal of an inode to/from a list. If we are not tied > to a list lock, we could update the counters when inodes are > initialised or destroyed, but to do that we need to convert the > counters to be per-cpu (i.e. independent of a lock). This means that > we have the freedom to change the list/locking implementation > without needing to care about the counters. > > Based on a patch originally from Eric Dumazet. > > Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx> Looks good except for a spurious whitespace change in inode_init_early. Reviewed-by: Christoph Hellwig <hch@xxxxxx> -- 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
