From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: davej@redhat.com, alex-kernel@digriz.org.uk,
Alexander Clouter <alex@digriz.org.uk>,
cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] (1/3) cpufreq_ondemand - 01_ignore-nice.diff
Date: Sun, 20 Feb 2005 15:51:57 +0100 [thread overview]
Message-ID: <20050220145157.GC20702@isilmar.linta.de> (raw)
In-Reply-To: <1108908764.6282.59.camel@laptopd505.fenrus.org>
On Sun, Feb 20, 2005 at 03:12:44PM +0100, Arjan van de Ven wrote:
> On Sun, 2005-02-20 at 13:15 +0000, Alexander Clouter wrote:
> > Adds support to cpufreq_ondemand to ignore 'nice' cpu time
>
> this increasingly starts to smell like it wants this policy in
> userspace.....
There are enough userspace cpufreq daemons already. However, the policy
decision back then was to prefer governing CPU frequencies in the following
order:
a) hardware
b) kernelspace
c) userspace
http://marc.theaimsgroup.com/?t=103053598900004&r=2&w=2
and two decisive posts:
http://marc.theaimsgroup.com/?l=linux-kernel&m=103056055008566&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=103056413012458&w=2
Thanks,
Dominik
next prev parent reply other threads:[~2005-02-20 14:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 13:15 [PATCH] (1/3) cpufreq_ondemand - 01_ignore-nice.diff Alexander Clouter
2005-02-20 14:12 ` Arjan van de Ven
2005-02-20 14:51 ` Dominik Brodowski [this message]
2005-02-20 14:53 ` Dominik Brodowski
2005-02-20 18:14 ` Alexander Clouter
2005-02-20 20:59 ` PCS
2005-02-21 11:41 ` Bruno Ducrot
2005-02-20 16:14 ` Eric Piel
2005-02-21 10:20 ` Eric Piel
2005-02-21 10:27 ` Alexander Clouter
2005-02-21 12:58 ` Eric Piel
2005-02-21 15:54 ` Dominik Brodowski
2005-02-21 13:11 ` Stefan Seyfried
2005-02-21 13:31 ` Eric Piel
-- strict thread matches above, loose matches on Subject: below --
2005-02-21 18:05 Pallipadi, Venkatesh
2005-05-10 22:30 Alexander Clouter
2005-05-11 1:30 ` Dave Jones
2005-05-11 2:38 ` Dave Jones
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=20050220145157.GC20702@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=alex-kernel@digriz.org.uk \
--cc=alex@digriz.org.uk \
--cc=arjan@infradead.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.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.