From: Namhyung Kim <namhyung@gmail.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: acme@kernel.org, jolsa@kernel.org, mitake@dcl.info.waseda.ac.jp,
aswin@hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/9] perf bench: Add --repeat option
Date: Thu, 19 Jun 2014 15:14:49 +0900 [thread overview]
Message-ID: <877g4d8lye.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1402942467-10671-2-git-send-email-davidlohr@hp.com> (Davidlohr Bueso's message of "Mon, 16 Jun 2014 11:14:19 -0700")
Hi Davidlohr,
On Mon, 16 Jun 2014 11:14:19 -0700, Davidlohr Bueso wrote:
> There are a number of benchmarks that do single runs and
> as a result does not really help users gain a general idea
> of how the workload performs. So the user must either manually
> do multiple runs or just use single bogus results.
>
> This option will enable users to specify the amount of runs
> (arbitrarily defaulted to 5) through the '--repeat' option.
> Add it to perf-bench instead of implementing it always in
> each specific benchmark.
By adding a top-level option, I think it should be applied to all
benchmaks - but I guess it only supports sched messaging and futex,
right?
Also it makes benchmarks to run 5 times (by default) even if the option
is not given at all, is that your intention?
Thanks,
Namhyung
>
> Signed-off-by: Davidlohr Bueso <davidlohr@hp.com>
> ---
> tools/perf/Documentation/perf-bench.txt | 4 ++++
> tools/perf/bench/bench.h | 1 +
> tools/perf/builtin-bench.c | 7 +++++++
> 3 files changed, 12 insertions(+)
>
> diff --git a/tools/perf/Documentation/perf-bench.txt b/tools/perf/Documentation/perf-bench.txt
> index 4464ad7..fd70928 100644
> --- a/tools/perf/Documentation/perf-bench.txt
> +++ b/tools/perf/Documentation/perf-bench.txt
> @@ -16,6 +16,10 @@ This 'perf bench' command is a general framework for benchmark suites.
>
> COMMON OPTIONS
> --------------
> +-r::
> +--repeat=::
> +Specify amount of times to repeat the run (default 5).
> +
> -f::
> --format=::
> Specify format style.
> diff --git a/tools/perf/bench/bench.h b/tools/perf/bench/bench.h
> index eba4670..3c4dd44 100644
> --- a/tools/perf/bench/bench.h
> +++ b/tools/perf/bench/bench.h
> @@ -43,5 +43,6 @@ extern int bench_futex_requeue(int argc, const char **argv, const char *prefix);
> #define BENCH_FORMAT_UNKNOWN -1
>
> extern int bench_format;
> +extern unsigned int bench_repeat;
>
> #endif
> diff --git a/tools/perf/builtin-bench.c b/tools/perf/builtin-bench.c
> index 1e6e777..820da6e 100644
> --- a/tools/perf/builtin-bench.c
> +++ b/tools/perf/builtin-bench.c
> @@ -104,9 +104,11 @@ static const char *bench_format_str;
>
> /* Output/formatting style, exported to benchmark modules: */
> int bench_format = BENCH_FORMAT_DEFAULT;
> +unsigned int bench_repeat = 5; /* default number of times to repeat the run */
>
> static const struct option bench_options[] = {
> OPT_STRING('f', "format", &bench_format_str, "default", "Specify format style"),
> + OPT_UINTEGER('r', "repeat", &bench_repeat, "Specify amount of times to repeat the run"),
> OPT_END()
> };
>
> @@ -226,6 +228,11 @@ int cmd_bench(int argc, const char **argv, const char *prefix __maybe_unused)
> goto end;
> }
>
> + if (bench_repeat == 0) {
> + printf("Invalid repeat option: Must specify a positive value\n");
> + goto end;
> + }
> +
> if (argc < 1) {
> print_usage();
> goto end;
next prev parent reply other threads:[~2014-06-19 6:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 18:14 [PATCH 0/9] perf bench: Updates for 3.17 Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 1/9] perf bench: Add --repeat option Davidlohr Bueso
2014-06-19 6:14 ` Namhyung Kim [this message]
2014-06-19 11:45 ` Davidlohr Bueso
2014-06-19 23:51 ` Namhyung Kim
2014-06-20 3:03 ` Davidlohr Bueso
2014-06-24 5:54 ` Namhyung Kim
2014-06-25 5:51 ` [tip:perf/core] " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 2/9] perf bench: sched-messaging: Redo runtime output Davidlohr Bueso
2014-06-19 19:30 ` Arnaldo Carvalho de Melo
2014-06-16 18:14 ` [PATCH 3/9] perf bench: sched-messaging: Support multiple runs Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 4/9] perf bench: sched-messaging: Plug memleak Davidlohr Bueso
2014-06-19 6:20 ` Namhyung Kim
2014-06-25 5:51 ` [tip:perf/core] perf bench " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 5/9] perf bench: futex: Use global --repeat option Davidlohr Bueso
2014-06-25 5:51 ` [tip:perf/core] perf bench " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 6/9] perf bench: futex: Replace --silent option with global --format Davidlohr Bueso
2014-06-19 16:38 ` Arnaldo Carvalho de Melo
2014-06-19 17:01 ` Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 7/9] perf bench: mem: -o and -n options are mutually exclusive Davidlohr Bueso
2014-06-25 5:52 ` [tip:perf/core] perf bench mem: The " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 8/9] perf bench: sched-messaging: Drop barf() Davidlohr Bueso
2014-06-25 5:52 ` [tip:perf/core] perf bench " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 9/9] perf bench: futex: Support operations for shared futexes Davidlohr Bueso
2014-06-19 16:41 ` Arnaldo Carvalho de Melo
2014-06-19 16:43 ` Davidlohr Bueso
2014-06-19 17:05 ` Arnaldo Carvalho de Melo
2014-06-19 19:48 ` Darren Hart
2014-06-25 17:07 ` Davidlohr Bueso
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=877g4d8lye.fsf@sejong.aot.lge.com \
--to=namhyung@gmail.com \
--cc=acme@kernel.org \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
/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