RE: [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch

Bill Huey (hui) wrote:
> 
> Good to know that. What did the output reveal ?
> 
> What's your intended use again summarized ? futex contention ? I'll
> read the first posting again.
> 

Earlier I used latency_trace and figured that there was read contention
on mm->mmap_sem during call to _rt_down_read by java threads
when I was running volanomark.  That caused the slowdown of the rt
kernel
compared to non-rt kernel.  The output from lock_stat confirm
that mm->map_sem was indeed the most heavily contended lock.

Tim
-
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/

---

• Follow-Ups:
  • Re: [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch
    • From: Bill Huey (hui) <[email protected]>

• References:
  • Re: [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch
    • From: Bill Huey (hui) <[email protected]>

• Prev by Date: [PATCH] sata_nv: add suspend/resume support v3 (Resubmit)
• Next by Date: Re: [UPDATED PATCH] fix memory corruption from misinterpreted bad_inode_ops return values
• Previous by thread: Re: [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch
• Next by thread: Re: [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]