On Tue, 2013-06-11 at 03:14 -0700, Paul E. McKenney wrote: > > > Off-topic, although I am in this community for several years, > > I am not exactly clear with this problem. > > > > 1) In general case, which lock is the most competitive in the kernel? what > > it protects for? > > 2) In which special case, which lock is the most competitive in the kernel? > > what it protects for? > > 3) In general case, which list is the most hot list? > > 4) In which special case, which list is the most hot list? > > Others would know better than I, but mmap_sem has been called out as a
If the contention is with mmap_sem, then I doubt this is going to help much, as that's a sleeping rw semaphore. Now, rw semaphores are implemented with raw spinlocks, but I doubt that would be the main point of contention, compared to the sleeping part. -- Steve > prime offender for some workloads. There is of course some debate as > to whether the fault lies mmap_sem or with the workloads. There have > been some efforts to solve this one on LKML, plus some in academia have > worked on this as well: > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
