lkml.org 
[lkml]   [2014]   [Nov]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v2] Perf Bench: Locking Microbenchmark
From
Date
On Fri, 2014-11-21 at 12:57 -0300, Arnaldo Carvalho de Melo wrote:
> >
> > Test machine is a 8-sockets 80 cores Westmere system HT-off on v3.17-rc6.
> >
> > AIM7 AIM7 perf-bench perf-bench
> > Users Jobs/min Jobs/min/child Ops/sec Ops/sec/child
> > 500 119668.25 239.34 104249 208
> > 600 126074.90 210.12 106136 176
> > 700 128662.42 183.80 106175 151
> > 800 119822.05 149.78 106290 132
> > 900 106150.25 117.94 105230 116
> > 1000 104681.29 104.68 106489 106
> >
> > Perf trace for AIM7 fserver:
>
> I will rename this from "Perf trace for AIM7 fserver" to "Perf report
> for AIM7 fserver", as there is a 'perf trace' tool and that produces
> different output, etc.
>

I will make this changes for the next revision.

> > 14.51% reaim [kernel.kallsyms] [k] osq_lock
> > 4.98% reaim reaim [.] add_long
> > 4.98% reaim reaim [.] add_int
> > 4.31% reaim [kernel.kallsyms] [k] mutex_spin_on_owner
> > ...
> >
> > Perf trace of perf bench creat
>
> Ditto and here will replace 'perf bench creat' with the new naming:
> "perf bench locking vfs", right?
>

Yes perf bench creat is suppose to be perf bench vfs. I will make the
correction for the next revision.





\
 
 \ /
  Last update: 2014-11-21 20:21    [W:0.048 / U:1.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site