From: Peter Zijlstra <peterz@infradead.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
"Kok, Auke-jan H" <auke-jan.h.kok@intel.com>
Subject: Re: [PATCH] sched: Provide iowait counters
Date: Sat, 25 Jul 2009 19:41:14 +0200 [thread overview]
Message-ID: <1248543674.5780.36.camel@laptop> (raw)
In-Reply-To: <4A6B35F7.2030804@linux.intel.com>
On Sat, 2009-07-25 at 09:42 -0700, Arjan van de Ven wrote:
>
> In case you wonder why you need both tools, and can't just use one: we
> wondered the same, but it turns out that if you only build
> Tool Two, you don't get a good overview of what is going on on a
> higher level. It's like looking at the world via a microscope all the
> time,
I'd be thinking you could compose your ms based picture on the sample
data. For instance, if you sample on cpu-clock at 100kHz, then a 100
samples get you a full blue slice, 50 get you a 50% blue slice, etc.
Of course, since its sample based, you can miss some detail, but I think
you're looking at the large picture anyway.
Would this work?
next prev parent reply other threads:[~2009-07-25 17:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 18:31 [PATCH] sched: Provide iowait counters Arjan van de Ven
2009-07-20 19:16 ` Peter Zijlstra
2009-07-20 19:31 ` Arjan van de Ven
2009-07-20 19:42 ` Steven Rostedt
2009-07-20 20:11 ` Peter Zijlstra
2009-07-20 20:26 ` Steven Rostedt
2009-07-20 20:38 ` Peter Zijlstra
2009-07-20 21:03 ` Steven Rostedt
2009-07-25 4:22 ` Andrew Morton
2009-07-25 4:33 ` Arjan van de Ven
2009-07-25 4:40 ` Andrew Morton
2009-07-25 4:48 ` Arjan van de Ven
2009-07-25 5:04 ` Andrew Morton
2009-07-25 6:05 ` Peter Zijlstra
2009-07-25 7:21 ` Andrew Morton
2009-07-25 16:42 ` Arjan van de Ven
2009-07-25 17:41 ` Peter Zijlstra [this message]
2009-07-25 17:56 ` Arjan van de Ven
2009-07-25 18:25 ` Arjan van de Ven
2009-08-03 13:21 ` [tip:sched/core] " tip-bot for Arjan van de Ven
2009-09-02 7:00 ` tip-bot for Arjan van de Ven
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=1248543674.5780.36.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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