Messages in this thread | | | Date | Wed, 19 Jun 2013 21:58:22 +0200 | From | Oleg Nesterov <> | Subject | Re: [PATCH 0/3] tracing/perf: perf_trace_buf/perf_xxx hacks. |
| |
On 06/19, David Ahern wrote: > > On 6/19/13 11:51 AM, Oleg Nesterov wrote: >> >> not sure these numbers actually mean >> something, but still.
Yes.
>> So, the test-case: >> >> int pipe1[2], pipe2[2]; > > Same as "perf bench sched pipe"
You just cruelly disclosed the fact that I do not use perf.
Thanks. So,
# perf record -e sched:sched_switch -p1 & [1] 516 # perf bench sched pipe
3 times.
before:
Total time: 30.119 [sec]
30.119501 usecs/op 33201 ops/sec
Total time: 30.634 [sec]
30.634105 usecs/op 32643 ops/sec
Total time: 30.100 [sec]
30.100209 usecs/op 33222 ops/sec
after:
Total time: 29.645 [sec]
29.645941 usecs/op 33731 ops/sec
Total time: 29.759 [sec]
29.759075 usecs/op 33603 ops/sec
Total time: 29.803 [sec]
29.803522 usecs/op 33553 ops/sec
Hmm. Actually sched-pipe.c is a bit more "heavy", it does switch_mm(). And I used taskset. But it seems that this test-case shows the similar results.
Oleg.
| |