From: Hitoshi Mitake <h.mitake@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>,
Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Subject: Re: [PATCH] perf bench: Flush stdout before starting bench suite
Date: Tue, 08 Jan 2013 22:59:36 +0900 [thread overview]
Message-ID: <87r4lv93nb.wl%h.mitake@gmail.com> (raw)
In-Reply-To: <1357637966-8216-1-git-send-email-namhyung@kernel.org>
At Tue, 8 Jan 2013 18:39:26 +0900,
Namhyung Kim wrote:
>
> From: Namhyung Kim <namhyung.kim@lge.com>
>
> perf bench prints header message for bench suite before starting the
> benchmark. However if the stdout is redirected to a file and bench
> suite forks child processes this (and possibly other debugging
> messages too) will be repeated multiple times.
>
> $ perf bench sched messaging
> # Running sched/messaging benchmark...
> # 20 sender and receiver processes per group
> # 10 groups == 400 processes run
>
> Total time: 0.100 [sec]
>
> $ perf bench sched messaging > result.txt
> $ wc -l result.txt
> 391
>
> In this file, there were so many "Running sched/messaging benchmark..."
> lines. This was because stdout is converted to fully-buffered due to
> the redirection and inherited child processes. Other lines are printed
> after reaping all those tasks.
>
> So fix it by flushing stdout before starting bench suites.
Thanks a lot, I couldn't notice this problem.
Acked-by: Hitoshi Mitake <h.mitake@gmail.com>
>
> Cc: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/builtin-bench.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/perf/builtin-bench.c b/tools/perf/builtin-bench.c
> index cae9a5fd2ecf..afd1255a632f 100644
> --- a/tools/perf/builtin-bench.c
> +++ b/tools/perf/builtin-bench.c
> @@ -159,6 +159,7 @@ static void all_suite(struct bench_subsys *subsys) /* FROM HERE */
> printf("# Running %s/%s benchmark...\n",
> subsys->name,
> suites[i].name);
> + fflush(stdout);
>
> argv[1] = suites[i].name;
> suites[i].fn(1, argv, NULL);
> @@ -225,6 +226,7 @@ int cmd_bench(int argc, const char **argv, const char *prefix __maybe_unused)
> printf("# Running %s/%s benchmark...\n",
> subsystems[i].name,
> subsystems[i].suites[j].name);
> + fflush(stdout);
> status = subsystems[i].suites[j].fn(argc - 1,
> argv + 1, prefix);
> goto end;
> --
> 1.7.11.7
>
>
next prev parent reply other threads:[~2013-01-08 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 9:39 [PATCH] perf bench: Flush stdout before starting bench suite Namhyung Kim
2013-01-08 13:59 ` Hitoshi Mitake [this message]
2013-01-25 11:32 ` [tip:perf/core] " tip-bot for Namhyung Kim
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=87r4lv93nb.wl%h.mitake@gmail.com \
--to=h.mitake@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=namhyung.kim@lge.com \
--cc=namhyung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox