Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752535AbZGYEsY (ORCPT ); Sat, 25 Jul 2009 00:48:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750949AbZGYEsX (ORCPT ); Sat, 25 Jul 2009 00:48:23 -0400 Received: from mga10.intel.com ([192.55.52.92]:64356 "EHLO fmsmga102.fm.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750933AbZGYEsX (ORCPT ); Sat, 25 Jul 2009 00:48:23 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.43,268,1246863600"; d="scan'208";a="477869731" Message-ID: <4A6A8E96.7050509@linux.intel.com> Date: Fri, 24 Jul 2009 21:48:22 -0700 From: Arjan van de Ven User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Andrew Morton CC: Linux Kernel Mailing List , Ingo Molnar , Peter Zijlstra , "Kok, Auke-jan H" Subject: Re: [PATCH] sched: Provide iowait counters References: <4A64B813.1080506@linux.intel.com> <20090724212220.afa278ee.akpm@linux-foundation.org> <4A6A8AFE.1010608@linux.intel.com> <20090724214006.7380c3b4.akpm@linux-foundation.org> In-Reply-To: <20090724214006.7380c3b4.akpm@linux-foundation.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1598 Lines: 35 Andrew Morton wrote: > On Fri, 24 Jul 2009 21:33:02 -0700 Arjan van de Ven wrote: > >> Andrew Morton wrote: >>> On Mon, 20 Jul 2009 11:31:47 -0700 Arjan van de Ven 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) > > See include/linux/sched.h's definition of task_delay_info - u64 > blkio_delay is in nanoseconds. It uses > do_posix_clock_monotonic_gettime() internally. looks like it does.. to bad we don't expose that data in a /proc//delay or something field like we do with the scheduler info... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/