Return-path: Received: from casper.infradead.org ([85.118.1.10]:41079 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755643AbZJHNp2 (ORCPT ); Thu, 8 Oct 2009 09:45:28 -0400 Date: Thu, 8 Oct 2009 06:45:21 -0700 From: Arjan van de Ven To: Mike Galbraith Cc: Frans Pop , Linux Kernel Mailing List , Ingo Molnar , Peter Zijlstra , 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> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, 08 Oct 2009 13:24:22 +0200 Mike Galbraith 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