On Fri, Oct 08, 2010 at 10:22:34AM +0200, Andi Kleen wrote: > Dave Chinner <david@xxxxxxxxxxxxx> writes: > > > From: Eric Dumazet <eric.dumazet@xxxxxxxxx> > > > > new_inode() dirties a contended cache line to get increasing > > inode numbers. This limits performance on workloads that cause > > significant parallel inode allocation. > > > > Solve this problem by using a per_cpu variable fed by the shared > > last_ino in batches of 1024 allocations. This reduces contention on > > the shared last_ino, and give same spreading ino numbers than before > > (i.e. same wraparound after 2^32 allocations). > > This doesn't help for Unix disk file systems, so not fully sure why you > need it for XFS. Currently i_ino is assigned for every inode allocated using new_inode. It's pretty stupid as most callers simply don't need it. But Dave didn't want to make this series even more complicated than nessecary and leave sorting this out for later. -- 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
