From: Mike Galbraith <efault@gmx.de>
To: Arjan van de Ven <arjan@infradead.org>
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"
Date: Thu, 08 Oct 2009 16:15:12 +0200 [thread overview]
Message-ID: <1255011312.7294.3.camel@marge.simson.net> (raw)
In-Reply-To: <20091008064521.07fae137@infradead.org>
On Thu, 2009-10-08 at 06:45 -0700, Arjan van de Ven wrote:
> 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!
That explains.. a few things.
-Mike
prev parent reply other threads:[~2009-10-08 14:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 13:00 [.32-rc3] scheduler: iwlagn consistently high in "waiting for CPU" Frans Pop
2009-10-05 14:13 ` Frans Pop
2009-10-05 14:24 ` Arjan van de Ven
2009-10-06 15:49 ` Frans Pop
2009-10-07 17:10 ` Frans Pop
2009-10-07 18:10 ` Mike Galbraith
2009-10-07 18:34 ` Frans Pop
2009-10-08 4:05 ` Mike Galbraith
2009-10-08 6:23 ` Mike Galbraith
2009-10-08 13:40 ` Arjan van de Ven
2009-10-08 14:13 ` Mike Galbraith
2009-10-08 14:54 ` Mike Galbraith
2009-10-08 14:55 ` Frans Pop
2009-10-08 15:09 ` Arjan van de Ven
2009-10-08 18:23 ` Mike Galbraith
2009-10-08 20:34 ` Markus Trippelsdorf
2009-10-09 3:35 ` Mike Galbraith
2009-10-09 3:51 ` Markus Trippelsdorf
2009-10-08 20:59 ` Frans Pop
2009-10-09 3:04 ` Mike Galbraith
2009-10-09 6:35 ` Mike Galbraith
2009-10-09 7:13 ` Peter Zijlstra
2009-10-09 7:55 ` Sedat Dilek
2009-10-09 7:55 ` Sedat Dilek
2009-10-09 8:06 ` Peter Zijlstra
2009-10-09 8:06 ` Peter Zijlstra
2009-10-09 14:23 ` [tip:sched/urgent] sched: Update the clock of runqueue select_task_rq() selected tip-bot for Mike Galbraith
2009-10-09 16:27 ` [.32-rc3] scheduler: iwlagn consistently high in "waiting for CPU" Frans Pop
2009-10-09 20:06 ` Mike Galbraith
2009-10-08 15:30 ` [tip:timers/urgent] x86, timers: Check for pending timers after (device) interrupts tip-bot for Arjan van de Ven
2009-10-09 14:23 ` [tip:sched/urgent] Revert "x86, timers: Check for pending timers after (device) interrupts" tip-bot for Ingo Molnar
2009-10-08 11:24 ` [.32-rc3] scheduler: iwlagn consistently high in "waiting for CPU" Mike Galbraith
2009-10-08 13:09 ` Frans Pop
2009-10-08 13:18 ` Mike Galbraith
2009-10-08 13:45 ` Arjan van de Ven
2009-10-08 14:15 ` Mike Galbraith [this message]
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=1255011312.7294.3.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=arjan@infradead.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.