From: Arjan van de Ven <arjan@infradead.org>
To: Frans Pop <elendil@planet.nl>
Cc: 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: Mon, 5 Oct 2009 07:24:28 -0700 [thread overview]
Message-ID: <20091005072428.16ce40e4@infradead.org> (raw)
In-Reply-To: <200910051613.32631.elendil@planet.nl>
On Mon, 5 Oct 2009 16:13:31 +0200
Frans Pop <elendil@planet.nl> wrote:
> On Monday 05 October 2009, Frans Pop wrote:
> > With .32-rc3 I'm getting occasional skips from amarok while playing
> > music from an NFS share (3 today so far), something I've not had in
> > a long time.
> >
> > The reason looks to be that latencytop consistently shows 'iwlagn'
> > as the top affected process with "Scheduler: waiting for CPU".
> > Values of 100-140 ms occur frequently, but I've also seen higher
> > values (180, 207). I don't remember seeing iwlagn high in the list
> > before, but I have not checked earlier kernels yet.
> >
> > Added to that 'phy0' also frequently shows high with values of
> > 25-75 ms.
> >
> > The system is otherwise essentially idle. Other processes typically
> > show a latency < 5 ms.
>
> If I give the system some work to do (like compiling a kernel), the
> latencies on iwlagn and phy0 disappear (values < 5 ms).
> Is this related to ondemand frequency scaling?
shouldn't be.... but
can you do a 5 second or so timechart recording of this?
That will capture all scheduler delays as well as the P states etc....
(to do a timechart recording, first make sure debugfs is mounted, and
then do in tools/perf
./perf timechart record sleep 5
then you can turn it into an SVG with
./perf timechart
)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-10-05 14:24 UTC|newest]
Thread overview: 31+ 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 [this message]
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 8:06 ` Peter Zijlstra
2009-10-09 16:27 ` Frans Pop
2009-10-09 20:06 ` Mike Galbraith
2009-10-08 11:24 ` 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
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=20091005072428.16ce40e4@infradead.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).