On 2/28/14, 11:43 AM, Rodrigo Campos wrote:
There are ways (not sure if the patch is in) to track for lock contension using perf, but not sure (I think not easy at least) if the lock is not contended. As, if using glibc, lot of locks are implemented using futex and then solved entirely in userspace lot of times (at least without contention).
What patch are you referring to? You can trace system calls to catch all contention and wakeups. You can put probes at lock entry, exit and unlock entry to track lock accesses by address.
I started working on this end of last year, just haven't had time to work on the analysis side -- statistical analysis of lock times with ability to see individual events. All I have right now is python script that pretty prints the events.
David -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
