From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: cpufreq list <cpufreq@www.linux.org.uk>
Subject: Re: Dynamic frequency governor
Date: Fri, 17 Oct 2003 22:00:36 -0700 [thread overview]
Message-ID: <1066453236.7590.4.camel@ixodes.goop.org> (raw)
In-Reply-To: <CFF522B18982EA4481D3A3E23B83141C24B4AA@orsmsx407.jf.intel.com>
On Fri, 2003-10-17 at 14:14, Moore, Robert wrote:
> Hi all,
>
> I've been chartered to implement a multi-state algorithm for Linux;
> this will be a new governor that adjusts the CPU frequency based upon
> percent CPU utilization as reported from the kernel idle handler.
>
> Has any work been done (or is being done) in this area? I don't want to
> rewrite the wheel.
Speedfreq (http://www.goop.org/~jeremy/speedfreq) does this in
userspace. I'm not sure there's much win in putting it into the kernel,
but a better idle measurement would be nice (I use /proc/uptime, which
can only be reliably polled a couple of times a second).
J
next prev parent reply other threads:[~2003-10-18 5:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 21:14 Dynamic frequency governor Moore, Robert
2003-10-18 5:00 ` Jeremy Fitzhardinge [this message]
2003-10-18 5:58 ` Vivek Haldar
2003-10-19 21:34 ` Jeroen van der Vegt
2003-10-18 6:44 ` David Kar-Fai Tam
2003-12-22 21:41 ` David Kar-Fai Tam
2004-02-14 17:09 ` Dominik Brodowski
2003-10-19 13:24 ` Dave Jones
2003-10-20 15:40 ` Daniel Thor Kristjansson
-- strict thread matches above, loose matches on Subject: below --
2003-10-20 15:31 Moore, Robert
2003-10-20 15:39 ` Dave Jones
2003-10-20 16:33 Moore, Robert
2003-10-20 17:00 ` Dave Jones
2003-10-20 17:12 ` Daniel Thor Kristjansson
2003-10-20 17:25 ` Ducrot Bruno
2003-10-20 17:32 ` Dave Jones
2003-10-20 17:35 ` Ducrot Bruno
2003-10-20 18:10 ` Dave Jones
2003-10-20 23:28 ` Sven Dowideit
2003-10-20 17:08 Moore, Robert
2003-10-21 20:31 ` Dave Jones
2003-10-21 22:21 ` David Kar-Fai Tam
2003-10-21 23:19 ` 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=1066453236.7590.4.camel@ixodes.goop.org \
--to=jeremy@goop.org \
--cc=cpufreq@www.linux.org.uk \
--cc=robert.moore@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox