From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Sohaib Mohamed <sohaib.amhmd@gmail.com>,
irogers@google.com, Riccardo Mancini <rickyman7@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Fabian Hemmer <copy@copy.sh>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Unbuffered output when pipe/tee to a file
Date: Thu, 9 Dec 2021 20:30:06 +0100 [thread overview]
Message-ID: <YbJZPsCfXi8QUbfR@krava> (raw)
In-Reply-To: <YbJQOfeeAoJ1GzJZ@kernel.org>
On Thu, Dec 09, 2021 at 03:51:37PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Sun, Nov 28, 2021 at 04:34:05PM +0100, Jiri Olsa escreveu:
> > On Fri, Nov 19, 2021 at 08:14:08AM +0200, Sohaib Mohamed wrote:
> > > The output of Perf bench gets buffered when I pipe it to a file or to
> > > tee, in such a way that I can see it only at the end.
> > >
> > > E.g.
> > > $ perf bench internals synthesize -t
> > > < output comes out fine after each test run >
> > >
> > > $ perf bench internals synthesize -t | tee file.txt
> > > < output comes out only at the end of all tests >
> > >
> > > This patch resolves this issue for 'bench' and 'test' subcommands.
> >
> > I can reproduce this for bench, but not for test subcommand
> > other that that it makes sense to me
>
> I reproduced it, see my comment to Sohaib's message, its not at the end,
> its when the buffer fills up.
>
> From the "it makes sense to me" I'm deriving an Acked-by you, ok?
ok, yes
Acked-by: Jiri Olsa <jolsa@redhat.com>
jirka
>
> - Arnaldo
>
> > jirka
> >
> > >
> > > See, also:
> > > $ perf bench mem all | tee file.txt
> > > $ perf bench sched all | tee file.txt
> > > $ perf bench internals all -t | tee file.txt
> > > $ perf bench internals all | tee file.txt
> > >
> > > Suggested-by: Riccardo Mancini <rickyman7@gmail.com>
> > > Signed-off-by: Sohaib Mohamed <sohaib.amhmd@gmail.com>
> > > ---
> > > v1 -> v2:
> > > - Use setvbuf(), instead of sprinkling fflush() calls and missing some places.
> > >
> > > v1: https://lore.kernel.org/linux-perf-users/20211112215313.108823-1-sohaib.amhmd@gmail.com/
> > > ---
> > > tools/perf/builtin-bench.c | 5 +++--
> > > tools/perf/tests/builtin-test.c | 3 +++
> > > 2 files changed, 6 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/tools/perf/builtin-bench.c b/tools/perf/builtin-bench.c
> > > index d0895162c2ba..d291f3a8af5f 100644
> > > --- a/tools/perf/builtin-bench.c
> > > +++ b/tools/perf/builtin-bench.c
> > > @@ -226,7 +226,6 @@ static void run_collection(struct collection *coll)
> > > if (!bench->fn)
> > > break;
> > > printf("# Running %s/%s benchmark...\n", coll->name, bench->name);
> > > - fflush(stdout);
> > >
> > > argv[1] = bench->name;
> > > run_bench(coll->name, bench->name, bench->fn, 1, argv);
> > > @@ -247,6 +246,9 @@ int cmd_bench(int argc, const char **argv)
> > > struct collection *coll;
> > > int ret = 0;
> > >
> > > + /* Unbuffered output */
> > > + setvbuf(stdout, NULL, _IONBF, 0);
> > > +
> > > if (argc < 2) {
> > > /* No collection specified. */
> > > print_usage();
> > > @@ -300,7 +302,6 @@ int cmd_bench(int argc, const char **argv)
> > >
> > > if (bench_format == BENCH_FORMAT_DEFAULT)
> > > printf("# Running '%s/%s' benchmark:\n", coll->name, bench->name);
> > > - fflush(stdout);
> > > ret = run_bench(coll->name, bench->name, bench->fn, argc-1, argv+1);
> > > goto end;
> > > }
> > > diff --git a/tools/perf/tests/builtin-test.c b/tools/perf/tests/builtin-test.c
> > > index 8cb5a1c3489e..d92ae4efd2e6 100644
> > > --- a/tools/perf/tests/builtin-test.c
> > > +++ b/tools/perf/tests/builtin-test.c
> > > @@ -606,6 +606,9 @@ int cmd_test(int argc, const char **argv)
> > > if (ret < 0)
> > > return ret;
> > >
> > > + /* Unbuffered output */
> > > + setvbuf(stdout, NULL, _IONBF, 0);
> > > +
> > > argc = parse_options_subcommand(argc, argv, test_options, test_subcommands, test_usage, 0);
> > > if (argc >= 1 && !strcmp(argv[0], "list"))
> > > return perf_test__list(argc - 1, argv + 1);
> > > --
> > > 2.25.1
> > >
>
> --
>
> - Arnaldo
>
next prev parent reply other threads:[~2021-12-09 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 6:14 [PATCH v2] Unbuffered output when pipe/tee to a file Sohaib Mohamed
2021-11-28 15:34 ` Jiri Olsa
2021-12-09 18:51 ` Arnaldo Carvalho de Melo
2021-12-09 19:30 ` Jiri Olsa [this message]
2021-12-09 18:50 ` Arnaldo Carvalho de Melo
2021-12-11 17:10 ` David Laight
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=YbJZPsCfXi8QUbfR@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=copy@copy.sh \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rickyman7@gmail.com \
--cc=sohaib.amhmd@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.