From: Ingo Molnar <mingo@kernel.org>
To: Josef Bacik <jbacik@fb.com>
Cc: a.p.zijlstra@chello.nl, mingo@redhat.com, acme@kernel.org,
linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] perf-sched: add option to merge like comms to lat output
Date: Fri, 22 May 2015 08:27:23 +0200 [thread overview]
Message-ID: <20150522062722.GB4736@gmail.com> (raw)
In-Reply-To: <1432243504-21235-1-git-send-email-jbacik@fb.com>
* Josef Bacik <jbacik@fb.com> wrote:
> Sometimes when debugging large multi-threaded applications it is helpful to
> collate all of the latency numbers into one bulk record to get an idea of what
> is going on. This patch does this by merging any entries that belong to the
> same comm into one entry and then spits out those totals. I've also sligtly
s/sligtly
slightly
> changed the output so you can see how many threads were merged in the
> processing. Thanks,
Useful feature!
> + OPT_BOOLEAN('m', "merge-by-comm", &sched.merge_by_comm,
> + "merge like tasks together in the output"),
Could you please make this the default behavior, and then add an
option to print more detailed latencies?
We generally try to output general overviews first, and then make it
easy to also output a more detailed view of information. That's how
perf report, perf top and perf stat (-d, -dd, -ddd) works in general.
Also, please post a before/after sample output in the changelog.
Thanks,
Ingo
prev parent reply other threads:[~2015-05-22 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 21:25 [PATCH] perf-sched: add option to merge like comms to lat output Josef Bacik
2015-05-22 6:27 ` Ingo Molnar [this message]
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=20150522062722.GB4736@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox