Date: Thu, 8 Oct 2009 06:45:21 -0700
From: Arjan van de Ven <arjan@infradead.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Frans Pop <elendil@planet.nl>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Ingo Molnar <mingo@elte.hu>, Peter Zijlstra <peterz@infradead.org>,
       linux-wireless@vger.kernel.org
Subject: Re: [.32-rc3] scheduler: iwlagn consistently high in "waiting for
 CPU"
Message-ID: <20091008064521.07fae137@infradead.org>
In-Reply-To: <1255001062.7500.1.camel@marge.simson.net>
References: <200910051500.55875.elendil@planet.nl>
	<200910061749.02805.elendil@planet.nl>
	<200910071910.53907.elendil@planet.nl>
	<200910072034.57511.elendil@planet.nl>
	<1255001062.7500.1.camel@marge.simson.net>
Organization: Intel
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 812
Lines: 24

On Thu, 08 Oct 2009 13:24:22 +0200
Mike Galbraith <efault@gmx.de> wrote:
> Latencytop was accounting uninterruptible and interruptible sleep
> time up to 5ms, which is not the latency the user is looking for.

it is for everything but the scheduler latency!

latencytop wants to show where you're waiting for disk, etc etc.
that's not "time on runqueue".

for the scheduler delays a whole different codepath is used!


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/