From: David Ahern <dsahern@gmail.com>
To: Ingo Molnar <mingo@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v1)
Date: Tue, 15 Nov 2016 08:14:24 -0700 [thread overview]
Message-ID: <468ed743-a7e9-44e4-6fcc-5853ab49447e@gmail.com> (raw)
In-Reply-To: <20161115073413.GA7016@gmail.com>
On 11/15/16 12:34 AM, Ingo Molnar wrote:
>
> * Namhyung Kim <namhyung@kernel.org> wrote:
>
>>>> By default it shows the individual schedule events, including the time between
>>>> sched-in events for the task, the task scheduling delay (time between wakeup
>>>> and actually running) and run time for the task:
>>>>
>>>> time cpu task name[tid/pid] b/n time sch delay run time
>>>> ------------- ---- -------------------- --------- --------- ---------
>>>> 79371.874569 [11] gcc[31949] 0.014 0.000 1.148
>>>> 79371.874591 [10] gcc[31951] 0.000 0.000 0.024
>>>> 79371.874603 [10] migration/10[59] 3.350 0.004 0.011
>>>> 79371.874604 [11] <idle> 1.148 0.000 0.035
>>>> 79371.874723 [05] <idle> 0.016 0.000 1.383
>>>> 79371.874746 [05] gcc[31949] 0.153 0.078 0.022
>>>> ...
>>>
>>> What does the 'b/n' abbreviation stand for? 'Between'? Could we call the column
>>> 'sch wait' instead, or so?
>>
>> Looks better, or what about 'wait time'?
>
> Works for me!
That column generically is time not running -- time between the last sched out and the current sched in. It could be expected (sleep, select, read, ...), waiting for a resource (disk I/O, mutex) or preemption.
>
>> I'd go with the first option - simply adding arrows. It's good enough to
>> identify each function IMHO.
>
> Ok!
I'd prefer the arrows too for a default. Color can be an add-on option.
next prev parent reply other threads:[~2016-11-15 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 16:12 Namhyung Kim
2016-11-14 16:12 ` [PATCH RESEND 1/7] perf symbol: Print symbol offsets conditionally Namhyung Kim
2016-11-14 16:12 ` [PATCH 2/7] perf sched timehist: Introduce timehist command Namhyung Kim
2016-11-14 16:12 ` [PATCH 3/7] perf sched timehist: Add summary options Namhyung Kim
2016-11-14 16:12 ` [PATCH 4/7] perf sched timehist: Add -w/--wakeups option Namhyung Kim
2016-11-14 16:12 ` [PATCH 5/7] perf sched timehist: Add call graph options Namhyung Kim
2016-11-14 16:12 ` [PATCH 6/7] perf sched timehist: Add -V/--cpu-visual option Namhyung Kim
2016-11-14 16:12 ` [PATCH 7/7] perf sched: Add documentation for timehist options Namhyung Kim
2016-11-14 16:26 ` [PATCHSET 0/7] perf sched: Introduce timehist command, again (v1) David Ahern
2016-11-15 6:42 ` Ingo Molnar
2016-11-15 6:55 ` Namhyung Kim
2016-11-15 7:34 ` Ingo Molnar
2016-11-15 15:14 ` David Ahern [this message]
2016-11-15 15:32 ` Namhyung Kim
2016-11-15 18:25 ` David Ahern
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=468ed743-a7e9-44e4-6fcc-5853ab49447e@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®