From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: gallir@uib.es
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: kapm-idled Funny in 2.4.10-ac12?
Date: Fri, 12 Oct 2001 19:08:52 +0100 (BST) [thread overview]
Message-ID: <E15s6js-0008Pf-00@the-village.bc.nu> (raw)
In-Reply-To: <20011012193019.A612@linux.uib.es> from "Ricardo Galli" at Oct 12, 2001 07:30:19 PM
> I am having almost the same problem in 2.4.12-ac1:
>
> gallir@linux:~$ uname -a
> Linux linux 2.4.12-ac1 #2 Fri Oct 12 19:01:03 CEST 2001 i686 unknown
>
> kapm-idled consumes a 14% of CPU (in a P3 1GHz)
>
> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
> 3 root 17 0 0 0 0 RW 14.3 0.0 1:17 kapm-idled
>
> The same happens with vanilla Linus tree (tested up to 2.4.11). In a P2,
> CPU consuption was more than 85%.
>
> The CPU's temperature, while the system idle, is more than 4 degrees (C)
> higher than the same conditions with the kapm-idled disabled.
I've been reading throught the APM spec and code a bit further. The more
I read the more I wonder quite how our idle code is meant to work and what
kind of beer was overconsumed during its writing.
There are two glaring issues I can see right now
#1 The BIOS might sleep for a tick, but it is also is allowed to slow
the cpu and return straight back to us.
If it returns back to us we spin in a tight loop at the lower clock
speed calling the APM bios. Not ideal.
Just fixed that in my tree for the next -ac
#2 We test system_idle() nr_running==1, but we spent all our time
pretending we aren't running. Im not 100% sure the test is safe
yet
Alan
next parent reply other threads:[~2001-10-12 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011012193019.A612@linux.uib.es>
2001-10-12 18:08 ` Alan Cox [this message]
2001-10-12 14:12 Kent Borg
2001-10-12 14:21 ` Alan Cox
2001-10-12 14:32 ` Peter T. Breuer
2001-10-12 14:35 ` Kent Borg
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=E15s6js-0008Pf-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gallir@uib.es \
--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®