From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Taeung Song <treeze.taeung@gmail.com>
Subject: Re: [PATCH v3] perf tools: Document --children option in more detail
Date: Tue, 21 Apr 2015 13:46:40 -0300 [thread overview]
Message-ID: <20150421164640.GG11111@kernel.org> (raw)
In-Reply-To: <20150421161629.GG8483@danjae.kornet>
Em Wed, Apr 22, 2015 at 01:16:29AM +0900, Namhyung Kim escreveu:
> On Tue, Apr 21, 2015 at 12:41:33PM -0300, Arnaldo Carvalho de Melo wrote:
> > > +++ b/tools/perf/Documentation/overhead-calculation.txt
> > I think Ingo suggested that you renamed this file to include the word
> > "callchain" in it, no? looking at "overhead-calculation" I feel like I
> > first have to open it to figure out what kind of overhead is this,
> > perhaps it would be better named:
> > tools/perf/Documentation/callchain-overhead.txt
> > ?
> Please see my reply to the Ingo's post. I think he agreed on this name.
I still find it confusing for the file name, where there is no context,
from just the file name when one does a 'ls tools/perf/Documentatoin' to
figure out about what overhead that is referring to.
So, perhaps a longer name:
tools/perf/Documentation/callchain-overhead-calculation.txt
?
Inside perf-{record,top}.txt, yeah, we have context, we know that this
is about post processing, formatting, etc.
<SNIP>
> > > +--no-children option on the command line or by adding 'report.children
> > > += false' or 'top.children = false' in the perf config file.
> >
> > One can as well use the OPTION_FOO shortening mechanism and instead use:
> >
> > perf report --no-ch
> >
> > Which is enough to disambiguate it from "--no-column-widths" and "--no-cpu".
>
> Are you saying that you want to add the short form instead of the full
> --no-chlidren name? I think we need to verbose in the manpage at
> least and it might not work in the future if some --chxxx option is
> added.
Perhaps:
"--no-children option on the command line or by adding 'report.children = false'
or 'top.children = false' in the perf config file.
A shorter form on the command line can be used, for instance '--no-ch'
is unambiguous at the time of this writing."
> > > diff --git a/tools/perf/Documentation/perf-report.txt b/tools/perf/Documentation/perf-report.txt
> > > index 4879cf638824..b7bb298deee3 100644
> > > --- a/tools/perf/Documentation/perf-report.txt
> > > +++ b/tools/perf/Documentation/perf-report.txt
> > > @@ -193,6 +193,7 @@ OPTIONS
> > > Accumulate callchain of children to parent entry so that then can
> > > show up in the output. The output will have a new "Children" column
> > > and will be sorted on the data. It requires callchains are recorded.
> > > + See the `overhead calculation' section for more details.
> >
> > `callchain overhead'
>
> Do you prefer this name to 'overhead calculation'? For me, it looks
It is ok with me "overhead calculation", as mentioned previously in this
message, the context in this perf-report.txt file should make it clear
that the overhead is about callchains.
> like saying about how much overhead will be added if we enabled
> callchains at perf record time or processing them at perf report time.
Ok.
- Arnaldo
next prev parent reply other threads:[~2015-04-21 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 12:28 [PATCH v3] perf tools: Document --children option in more detail Namhyung Kim
2015-04-21 15:41 ` Arnaldo Carvalho de Melo
2015-04-21 16:16 ` Namhyung Kim
2015-04-21 16:46 ` Arnaldo Carvalho de Melo [this message]
2015-04-22 6:09 ` Namhyung Kim
2015-04-22 11:49 ` Arnaldo Carvalho de Melo
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=20150421164640.GG11111@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=treeze.taeung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox