Bill Huey (hui) wrote: > Can you sort the output ("sort -n" what ever..) and post it without > the zeroed entries ? > > I'm curious about how that statistical spike compares to the rest of > the system activity. I'm sure that'll get the attention of Peter as > well and maybe he'll do something about it ? :) >
Here's the lockstat trace. You can cross reference it with my earlier post. http://marc.theaimsgroup.com/?l=linux-kernel&m=116743637422465&w=2 The contention happened on mm->mmap_sem shared by the java threads during futex_wake's invocation of _rt_down_read. Tim @contention events = 247149 @failure_events = 146 @lookup_failed_scope = 175 @lookup_failed_static = 43 @static_found = 16 [1, 113, 77 -- 32768, 0] {tcp_init, net/ipv4/tcp.c, 2426} [2, 759, 182 -- 1, 0] {lock_kernel, -, 0} [13, 0, 7 -- 4, 0] {kmem_cache_free, -, 0} [25, 3564, 9278 -- 1, 0] {lock_timer_base, -, 0} [56, 9528, 24552 -- 3, 0] {init_timers_cpu, kernel/timer.c, 1842} [471, 52845, 17682 -- 10448, 0] {sock_lock_init, net/core/sock.c, 817} [32251, 9024, 242 -- 256, 0] {init, kernel/futex.c, 2781} [173724, 11899638, 9886960 -- 11194, 0] {mm_init, kernel/fork.c, 369} - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/