From: Christian Vogel <vogel@skunk.physik.uni-erlangen.de>
To: Charles Lepple <clepple@ghz.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.0-test2: Never using pm_idle (CPU wasting power)
Date: Thu, 31 Jul 2003 16:44:57 +0200 [thread overview]
Message-ID: <20030731164457.A6993@skunk.physik.uni-erlangen.de> (raw)
In-Reply-To: <17207.216.12.38.216.1059660771.squirrel@www.ghz.cc>; from clepple@ghz.cc on Thu, Jul 31, 2003 at 10:12:51AM -0400
Hi,
On Thu, Jul 31, 2003 at 10:12:51AM -0400, Charles Lepple wrote:
> about this (haven't instrumented it all the way), it also appears that
> pm_idle is not being called (for up to an hour, in some cases). Sometimes
> it takes only a few minutes, and other times, it appears to kick in after
> heavy CPU usage (kernel compiles, cpuburn, etc.).
Yes, exactly. Up to the first time need_resched() returns true and
the outer while(1){ } loop loops to update the idle-variable. Unfortunately
this never was the case on my system for a long time...
Probably the idle loop uses this local variable to be more cache-friendly,
but then any module updating pm_idle should probably set need_resched
to force an update of the idle function pointer?
Chris
--
Read the OSI protocol specifications? I can't even *lift* them!
next prev parent reply other threads:[~2003-07-31 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 13:07 Christian Vogel
2003-07-31 14:12 ` Charles Lepple
2003-07-31 14:44 ` Christian Vogel [this message]
2003-07-31 22:45 ` Roger Larsson
2003-07-31 22:58 ` Robert Love
2003-07-31 23:26 ` Robert Love
2003-07-31 22:59 ` Andrew Morton
2003-08-01 9:18 ` Christian Vogel
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=20030731164457.A6993@skunk.physik.uni-erlangen.de \
--to=vogel@skunk.physik.uni-erlangen.de \
--cc=clepple@ghz.cc \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®