From: Ingo Molnar <mingo@elte.hu>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Cc: linux-kernel@vger.kernel.org,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Paul Mackerras" <paulus@samba.org>,
=?unknown-8bit?B?RnLDqWTDqXJpYw==?= Weisbecker
<fweisbec@gmail.com>
Subject: Re: [PATCH 0/3] perf bench: Clean and add document for perf-bench
Date: Tue, 10 Nov 2009 14:17:38 +0100 [thread overview]
Message-ID: <20091110131738.GA31158@elte.hu> (raw)
In-Reply-To: <1257853855-28934-1-git-send-email-mitake@dcl.info.waseda.ac.jp>
* Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> wrote:
> This patch series cleans bench/bench.h for readability and
> adds new document describing perf-bench.
>
> Hitoshi Mitake (3):
> perf bench: Clean bench/bench.h
> perf bench: Add new document of perf-bench
> perf bench: Modify command-list.txt for the entry of perf-bench
>
> tools/perf/Documentation/perf-bench.txt | 120 +++++++++++++++++++++++++++++++
> tools/perf/bench/bench.h | 16 ++---
> tools/perf/command-list.txt | 1 +
> 3 files changed, 128 insertions(+), 9 deletions(-)
> create mode 100644 tools/perf/Documentation/perf-bench.txt
Applied, thanks!
Btw., a small detail i noticed when running the pipe benchmark:
earth4:~/tip/tools/perf> ./perf bench sched pipe
(executing 1000000 pipe operations between two tasks)
Total time:5.076 sec
5.076232 usecs/op
196996 ops/sec
when i typed 'perf bench sched pipe' nothing happened for several
seconds. The command did not finish and no output was printed.
This might surprise users - it's always good to print a single line that
we are processing a benchmark. Maybe this could be printed from the
generic subcommand, something like:
running sched/pipe benchmark ...
What do you think?
Ingo
next prev parent reply other threads:[~2009-11-10 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 11:50 [PATCH 0/3] perf bench: Clean and add document for perf-bench Hitoshi Mitake
2009-11-10 11:50 ` [PATCH 1/3] perf bench: Clean bench/bench.h Hitoshi Mitake
2009-11-10 13:25 ` [tip:perf/bench] perf bench: Clean up bench/bench.h tip-bot for Ingo Molnar
2009-11-10 11:50 ` [PATCH 2/3] perf bench: Add new document of perf-bench Hitoshi Mitake
2009-11-10 13:25 ` [tip:perf/bench] perf bench: Add new document about perf-bench tip-bot for Hitoshi Mitake
2009-11-10 11:50 ` [PATCH 3/3] perf bench: Modify command-list.txt for the entry of perf-bench Hitoshi Mitake
2009-11-10 13:25 ` [tip:perf/bench] " tip-bot for Hitoshi Mitake
2009-11-10 13:17 ` Ingo Molnar [this message]
2009-11-10 14:43 ` [PATCH 0/3] perf bench: Clean and add document for perf-bench 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=20091110131738.GA31158@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
--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