From: Pavel Machek <pavel@suse.cz>
To: stewart@neuron.com, Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kapm-idled : is this a bug?
Date: Fri, 15 Dec 2000 23:40:37 +0100 [thread overview]
Message-ID: <20001215234037.F9506@bug.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0012111315350.4808-100000@duckman.distro.conectiva> <Pine.LNX.4.10.10012111343570.2897-100000@localhost>
In-Reply-To: <Pine.LNX.4.10.10012111343570.2897-100000@localhost>; from stewart@neuron.com on Mon, Dec 11, 2000 at 01:56:22PM -0500
Hi!
> 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.
I guess we should just put even normal idle thread to be visible in
ps. It is cleaner design, anyway.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
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-16 22:25 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
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 [this message]
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=20001215234037.F9506@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=stewart@neuron.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.