From: Ingo Molnar <mingo@elte.hu>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Cc: linux-kernel@vger.kernel.org,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Mike Galbraith" <efault@gmx.de>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
Frédéric_Weisbecker <fweisbec@gmail.com>
Subject: Re: [RFC][PATCH 7/7] Adding general performance benchmarking subsystem to perf.
Date: Tue, 3 Nov 2009 08:46:48 +0100 [thread overview]
Message-ID: <20091103074648.GG19928@elte.hu> (raw)
In-Reply-To: <20091103.133927.580735811043340004.mitake@dcl.info.waseda.ac.jp>
* Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> wrote:
>
> Adding general performance benchmarking subsystem to perf.
> This patch adds builtin-bench-pipe.c
>
> builtin-bench-pipe.c is a benchmark program
> to measure performance of pipe() system call.
> This benchmark is based on pipe-test-1m.c by Ingo Molnar.
> http://people.redhat.com/mingo/cfs-scheduler/tools/pipe-test-1m.c
>
> Signed-off-by: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Mike Galbraith <efault@gmx.de>
> ---
> tools/perf/builtin-bench-pipe.c | 89 +++++++++++++++++++++++++++++++++++++++
> 1 files changed, 89 insertions(+), 0 deletions(-)
> create mode 100644 tools/perf/builtin-bench-pipe.c
>
> diff --git a/tools/perf/builtin-bench-pipe.c b/tools/perf/builtin-bench-pipe.c
> new file mode 100644
> index 0000000..081515e
> --- /dev/null
> +++ b/tools/perf/builtin-bench-pipe.c
> @@ -0,0 +1,89 @@
> +/*
> + *
> + * builtin-bench-pipe.c
> + *
> + * pipe: Benchmark for pipe()
> + *
> + * Based on pipe-test-1m.c by Ingo Molnar <mingo@redhat.com>
> + * http://people.redhat.com/mingo/cfs-scheduler/tools/pipe-test-1m.c
> + * Ported to perf by Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
> + *
> + */
Ok, i think there's going to be quite a few of these benchmarks, so i'd
suggest you start a new directory for the benchmark modules:
tools/perf/bench/ for example.
We'll still have tools/perf/builtin-bench.c which represents the highest
level 'perf bench' tool - and new modules can be added by adding them to
bench/.
What do you think?
All in one, i very much like the modular direction you are taking here.
There will be a handful of more details i'm sure but once there's a good
base we can commit it - would you / will you be interested in extending
it further and adding more benchmark modules as well?
There's quite a few useful small benchmarks that people are using to
measure the kernel. Having a good collection of them in one place, with
standardized options and standardized output would be very useful.
Ingo
next prev parent reply other threads:[~2009-11-03 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 4:39 [RFC][PATCH 7/7] Adding general performance benchmarking subsystem to perf Hitoshi Mitake
2009-11-03 7:46 ` Ingo Molnar [this message]
2009-11-03 10:53 ` Hitoshi Mitake
2009-11-03 17:24 ` Ingo Molnar
2009-11-04 10:33 ` Hitoshi Mitake
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=20091103074648.GG19928@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
/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