mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kapm-idled using 45% CPU (why not 100%?)
Date: Sat, 31 Mar 2001 15:44:38 +1000	[thread overview]
Message-ID: <200103310544.f2V5icO07172@pcug.org.au> (raw)
In-Reply-To: Your message of Sat, 31 Mar 2001 03:35:04 +0200. <20010331033504.A7022@pcep-jamie.cern.ch>

Hi Jamie,

Jamie Lokier <lk@tantalophile.demon.co.uk> writes:
> Subject says it all.  On my laptop which is running 2.4.0, while the
> machine is completely idle "top" reports kapm-idled as usin about 45% of
> the CPU.  The remaining 55% is reported as idle time.

This is normal behaviour ... the current implementation of kapm-idled
means that it is sleeping some of the time, so the real idle process
actually gets some time.  I did a patch a while ago the got the kapm-idled
up to about 93-95%, but I didn;t think i was all that important.

> When the machine gets a little more active, the CPU time attributed to
> kapm-idled decreases while the 55% idle time increases to 85%!

Again this is normal (although it may not seem sensible).

> This is not caused be "top": I get the same 45% from "ps -l 3".
> 
> I remember when kapmd was reporting 100%.  Is the new behaviour
> intentional, and is it saving the maximum power on the laptop?

I have NEVER seen kapmd getting 100%.  You are probably getting
about as good power saving as you will get (unfortunately) although
don't hold me to that - I have heard of some laptops that get better
power savings when CONFIG_APM_CPU_IDLE was NOT set ...

Cheers,
Stephen

  reply	other threads:[~2001-03-31  5:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-31  1:35 Jamie Lokier
2001-03-31  5:44 ` Stephen Rothwell [this message]
2001-03-31  6:19 ` Richard Gooch

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=200103310544.f2V5icO07172@pcug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    /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®