From: Ingo Molnar <mingo@kernel.org>
To: Tuan Bui <tuan.d.bui@hp.com>
Cc: linux-kernel@vger.kernel.org, dbueso@suse.de,
a.p.zijlstra@chello.nl, paulus@samba.org, acme@kernel.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: Thu, 9 Oct 2014 09:21:43 +0200 [thread overview]
Message-ID: <20141009072143.GA21018@gmail.com> (raw)
In-Reply-To: <1412806419.2908.6.camel@u64>
* Tuan Bui <tuan.d.bui@hp.com> wrote:
> > > +static const struct option options[] = {
> > > + OPT_UINTEGER('s', "start", &start_nr_threads, "Numbers of processes to start"),
> > > + OPT_UINTEGER('e', "end", &end_nr_threads, "Numbers of process to end"),
> > > + OPT_UINTEGER('i', "increment", &increment_threads_by, "Number of threads to increment)"),
> > > + OPT_UINTEGER('r', "runtime", &bench_dur, "Specify benchmark runtime in seconds"),
> > > + OPT_END()
> > > +};
> >
> > Is this the kind of parameters that AIM7 takes as well?
> >
> > In any case, this is a very nice benchmarking utility.
>
> Yes these parameters are similar to what AIM7 take except for
> the runtime parameter. AIM7 does not have the option to
> specify how long the benchmark will run. Also in AIM7 you can
> also specify numbers of jobs per run which i did not include
> since i added a runtime parameter for the benchmark.
It might make sense to add that parameter - which would only be
allowed if no runtime is specified, or so.
I.e. to make it as easy for people to use this new tool when they
come with AIM7 benchmarking knowledge.
Thanks,
Ingo
prev parent reply other threads:[~2014-10-09 7:21 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
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 [this message]
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=20141009072143.GA21018@gmail.com \
--to=mingo@kernel.org \
--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=paulus@samba.org \
--cc=tuan.d.bui@hp.com \
/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).