From: Tuan Bui <tuan.d.bui@hp.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, dbueso@suse.de,
a.p.zijlstra@chello.nl, paulus@samba.org, artagnon@gmail.com,
jolsa@redhat.com, dvhart@linux.intel.com,
Aswin Chandramouleeswaran <aswin@hp.com>,
Jason Low <jason.low2@hp.com>,
akpm@linux-foundation.org, mingo@kernel.org
Subject: Re: [PATCH v2] Perf Bench: Locking Microbenchmark
Date: Fri, 21 Nov 2014 10:46:51 -0800 [thread overview]
Message-ID: <1416595611.3482.3.camel@u64> (raw)
In-Reply-To: <20141121155706.GB18625@kernel.org>
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.
next prev parent reply other threads:[~2014-11-21 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 15:57 [PATCH v2] Perf Bench: Locking Microbenchmark Arnaldo Carvalho de Melo
2014-11-21 16:04 ` Arnaldo Carvalho de Melo
2014-11-21 18:52 ` Tuan Bui
2014-11-21 18:46 ` Tuan Bui [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-20 19:06 Tuan Bui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1416595611.3482.3.camel@u64 \
--to=tuan.d.bui@hp.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=artagnon@gmail.com \
--cc=aswin@hp.com \
--cc=dbueso@suse.de \
--cc=dvhart@linux.intel.com \
--cc=jason.low2@hp.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).