From: Pekka Enberg <penberg@iki.fi>
To: David Ahern <dsahern@gmail.com>,
acme@ghostprotocols.net, linux-kernel@vger.kernel.org
Cc: namhyung@kernel.org, Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>, Jiri Olsa <jolsa@redhat.com>,
Stephane Eranian <eranian@google.com>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH 1/2] perf sched: Introduce timehist command - v2
Date: Mon, 02 Dec 2013 11:33:06 +0200 [thread overview]
Message-ID: <529C53D2.8020203@iki.fi> (raw)
In-Reply-To: <1385943795-11761-2-git-send-email-dsahern@gmail.com>
On 12/02/2013 02:23 AM, David Ahern wrote:
> 'perf sched timehist' provides an analysis of scheduling events.
>
> Example usage:
> perf sched record -- sleep 1
> perf sched timehist
>
> 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 "b/n time" mean?
I'm seeing rather large "sch delay" numbers on Fedora 19's default
kernel that seem like a data error of some sort:
4500.663117 [02] fix_client[7216] 0.007
18446744073708.033 1.786
Scheduling delays don't seem to be part of "-s" summary output. Why?
Pekka
next prev parent reply other threads:[~2013-12-02 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 0:23 [PATCH 0/2] perf: sched timehist command - v2 David Ahern
2013-12-02 0:23 ` [PATCH 1/2] perf sched: Introduce " David Ahern
2013-12-02 7:58 ` Namhyung Kim
2013-12-02 14:28 ` David Ahern
2013-12-02 9:33 ` Pekka Enberg [this message]
2013-12-02 14:33 ` David Ahern
2013-12-02 16:19 ` David Ahern
2013-12-02 0:23 ` [PATCH 2/2] perf sched: Add documentation for timehist options David Ahern
2013-12-02 6:07 ` Srikar Dronamraju
2013-12-02 12:38 ` Ingo Molnar
2013-12-02 7:41 ` Namhyung Kim
2013-12-02 14:37 ` 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=529C53D2.8020203@iki.fi \
--to=penberg@iki.fi \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=penberg@kernel.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