From: Tuan Bui <tuan.d.bui@hp.com>
To: Davidlohr Bueso <dbueso@suse.de>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, 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
Subject: Re: [RFC PATCH] Perf Bench: Locking Microbenchmark
Date: Wed, 08 Oct 2014 15:14:53 -0700 [thread overview]
Message-ID: <1412806493.2908.7.camel@u64> (raw)
In-Reply-To: <1412312253.27162.5.camel@linux-t7sj.site>
On Thu, 2014-10-02 at 21:57 -0700, Davidlohr Bueso wrote:
> On Wed, 2014-10-01 at 14:12 -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Oct 01, 2014 at 07:28:32AM +0200, Ingo Molnar escreveu:
> > > If you compare an strace of AIM7 steady state and 'perf bench
> > > lock' steady state, is it comparable, i.e. do the syscalls and
> >
> > Isn't "lock" too generic? Isn't this stressing some specific lock and if
> > so shouldn't that be made abundantly clear in the 'perf bench' test name
> > and in the docs?
>
> yeah, and 'perf bench locking creat' just doesn't sound right.
>
Do you have any suggestion on how i should name it?
next prev parent reply other threads:[~2014-10-08 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 23:49 [RFC PATCH] Perf Bench: Locking Microbenchmark Tuan Bui
2014-10-01 5:28 ` Ingo Molnar
2014-10-01 17:12 ` Arnaldo Carvalho de Melo
2014-10-03 4:57 ` Davidlohr Bueso
2014-10-08 22:14 ` Tuan Bui [this message]
2014-10-08 22:11 ` Tuan Bui
2014-10-03 4:52 ` Davidlohr Bueso
2014-10-08 22:13 ` Tuan Bui
2014-10-09 7:21 ` Ingo Molnar
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=1412806493.2908.7.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.