From: Arjan van de Ven <arjan@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
"Kok, Auke-jan H" <auke-jan.h.kok@intel.com>
Subject: Re: [PATCH] sched: Provide iowait counters
Date: Fri, 24 Jul 2009 21:33:02 -0700 [thread overview]
Message-ID: <4A6A8AFE.1010608@linux.intel.com> (raw)
In-Reply-To: <20090724212220.afa278ee.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Mon, 20 Jul 2009 11:31:47 -0700 Arjan van de Ven <arjan@linux.intel.com> wrote:
>
>> For counting how long an application has been waiting for (disk) IO,
>> there currently is only the HZ sample driven information available, while
>> for all other counters in this class, a high resolution version is
>> available via CONFIG_SCHEDSTATS.
>>
>> In order to make an improved bootchart tool possible, we also need
>> a higher resolution version of the iowait time.
>>
>> This patch below adds this scheduler statistic to the kernel.
>
> Doesn't this duplicate the delay accounting already available via the
> taskstats interface?
we have how long we wait. we do not have how long we iowait afaik...
at least not in nanosecond granularity. (We do have the sampled data, but that
is milisecond sampled data, not very useful for making charts based on time
to show the sequence of events)
next prev parent reply other threads:[~2009-07-25 4:33 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 [this message]
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
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=4A6A8AFE.1010608@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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