[lkml]   [2009]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/2] perf lock: New subcommand "lock" to perf for analyzing lock statistics
Hi Frederic,

Frederic Weisbecker wrote:

> This profile has been done using ftrace with perf right?

We not use perf, just operate it by debugfs, the test procedure
is like below:

case 1: disable all trace events:
echo nop > debugfs/tracing/current_tracer
echo > debugfs/tracing/set_event
run benchmarks

case 2: enable all trace events except lockdep:
echo nop > debugfs/tracing/current_tracer
echo *:* > debugfs/tracing/set_event
echo 0 > debugfs/tracing/events/lockdep/enable
run benchmarks

> In one of your previous mails, you showed us the difference
> of the size of by capturing either scheduler events
> or lock events.

It's not my work :-)


> And IIRC, the case of lock events resulted in a 100 MB
> whereas it was a small file for sched events.
> The overhead in the pagefault and mmap latency could then
> result in the fact we have much more events to save, walking
> through much more pages in perf buffer, then faulting more often,
> etc.
> Plus the fact various locks are taken in mmap and fault path,
> generating more lock events.
> Just a guess...

 \ /
  Last update: 2009-12-08 02:35    [W:0.050 / U:3.992 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site