public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick.Holloway@pyrites.org.uk (Nick Holloway)
To: linux-kernel@vger.kernel.org
Subject: Re: kapm-idled : is this a bug?
Date: 11 Dec 2000 15:45:36 -0000	[thread overview]
Message-ID: <912sr0$5va$1@alfie.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10012111151470.2070-100000@localhost> <Pine.LNX.4.21.0012111315350.4808-100000@duckman.distro.conectiva>

riel@conectiva.com.br (Rik van Riel) writes:
> 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?

We know it was an attempt to stop people complaining about the fact that
"kapm" was hogging the CPU.  Looks like it doesn't work.

At the time, I had a look at the kernel source, and came to the conclusion
that there was no easy way for the cpu accounting in "do_process_times()"
to automatically assign ticks from a particular process to the idle
process.

However, would it be possible for apm_cpu_idle() to periodically assign
the values for per_cpu_*time for the kernel thread to the idle process?
This isn't a performance critical part of the kernel, and would lead to
less false reports (as above).

-- 
 `O O'  | Nick.Holloway@pyrites.org.uk
// ^ \\ | http://www.pyrites.org.uk/
-
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/

  reply	other threads:[~2000-12-11 16:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-11 17:00 kapm-idled : is this a bug? stewart
2000-12-11  5:11 ` Robert M. Love
2000-12-11 15:16 ` Rik van Riel
2000-12-11 15:45   ` Nick Holloway [this message]
2000-12-11 18:56   ` stewart
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='912sr0$5va$1@alfie.demon.co.uk' \
    --to=nick.holloway@pyrites.org.uk \
    --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