Re: [RFC PATCH] Perf Bench: Locking Microbenchmark
From: Davidlohr Bueso
Date: Fri Oct 03 2014 - 00:53:26 EST
On Wed, 2014-10-01 at 07:28 +0200, Ingo Molnar wrote:
> If you compare an strace of AIM7 steady state and 'perf bench
> lock' steady state, is it comparable, i.e. do the syscalls and
> other behavioral patterns match up?
With more than 1000 users I'm seeing:
- 33.74% locking-creat [kernel.kallsyms] [k] mspin_lock â
+ mspin_lock â
+ __mutex_lock_slowpath â
+ mutex_lock â
- 7.97% locking-creat [kernel.kallsyms] [k] mutex_spin_on_owner â
+ mutex_spin_on_owner â
+ __mutex_lock_slowpath â
+ mutex_lock
Lower users count just shows the syscall entries.
Of course, the aim7 setup was running on a ramdisk, thus avoiding any IO
overhead in the traces.
Thanks,
Davidlohr
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/