On Fri, Dec 19, 2014 at 02:40:33PM -0500, Josef Bacik wrote: > When doing fs_mark tests I was noticing other things getting starved out of > doing operations while the fs was unmounting. This is because we protect all > super_block's s_inodes list with a global lock, which is kind of a bummer. > There doesn't seem to be any reason we do this so make it a per-sb lock. This > makes sure that we don't add latency to anybody trying to add/remove inodes from > the per sb list while somebody else is unmounting or evicting inodes. Thanks, > > Signed-off-by: Josef Bacik <jbacik@xxxxxx> I'll have a look at this on Monday, but in the mean time I proposed this 18 months ago for different reasons, and never got back to it: https://lkml.org/lkml/2013/7/31/15 Maybe you want to pick up someof the other sb inode list scalability mods out of that series as well? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- 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
