From: stewart@neuron.com
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kapm-idled : is this a bug?
Date: Mon, 11 Dec 2000 13:56:22 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.10.10012111343570.2897-100000@localhost> (raw)
In-Reply-To: <Pine.LNX.4.21.0012111315350.4808-100000@duckman.distro.conectiva>
very helpful.
Technical merits and voter intent aside, this behavior is misleading and
inconsistent with previous kernels. Tools like top or a CPU dock applet show
a constantly loaded CPU. Hacking them to deduct the load from 'kapm-idled'
seems like the wrong answer.
stewart
On Mon, 11 Dec 2000, Rik van Riel wrote:
> On Mon, 11 Dec 2000 stewart@neuron.com wrote:
>
> [snip whine]
>
> > I've consistently re-produced this on my Dell Latitude CS laptop. I'm
> > wondering if this will reduce battery life since the CPU is constantly
> > being loaded instead of properly idled.
>
> What do you suppose the 'idled' in 'kapm-idled' stands for?
>
> Rik
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-11 19:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 17:00 stewart
2000-12-11 5:11 ` Robert M. Love
2000-12-11 15:16 ` Rik van Riel
2000-12-11 15:45 ` Nick Holloway
2000-12-11 18:56 ` stewart [this message]
2000-12-11 19:26 ` Richard B. Johnson
2000-12-11 19:28 ` Mark Hahn
2000-12-11 23:49 ` Kurt Garloff
2000-12-15 22:40 ` Pavel Machek
2000-12-17 2:18 ` Jamie Lokier
2000-12-17 15:26 ` Igmar Palsenberg
2000-12-20 9:11 ` Pavel Machek
2000-12-21 11:00 ` Igmar Palsenberg
2000-12-21 12:28 ` Pavel Machek
2000-12-21 19:27 ` Albert D. Cahalan
2000-12-22 10:02 ` Pavel Machek
2000-12-22 18:50 ` Igmar Palsenberg
2000-12-22 18:45 ` Igmar Palsenberg
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=Pine.LNX.4.10.10012111343570.2897-100000@localhost \
--to=stewart@neuron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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®