From: Dominik Brodowski <linux@brodo.de>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "Therien, Guy" <guy.therien@intel.com>,
"Grover, Andrew" <andrew.grover@intel.com>,
cpufreq@www.linux.org.uk, "Nakajima,
Jun" <jun.nakajima@intel.com>, linux-acpi <linux-acpi@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-statedriver
Date: Tue, 21 Oct 2003 22:01:14 +0200 [thread overview]
Message-ID: <20031021200114.GB26971@brodo.de> (raw)
In-Reply-To: <CFF522B18982EA4481D3A3E23B83141C24B4BC@orsmsx407.jf.intel.com>
On Tue, Oct 21, 2003 at 10:12:14AM -0700, Moore, Robert wrote:
>
> This is exactly what I was looking at doing, looks like most of the work
> is done. I have some concerns about the actual algorithm used for
> changing the CPU frequency (20%/80%), but this of course can be tuned.
Well, so write a different governor, and feel free to use Venkatesh's code
as a base [it's GPLed, after all...]. I prefer to have several different
governors available, so that different users with different needs
can use different "policies".
> I suspect that CPUs that have the capability of changing frequency
> themselves would not use this particular governor.
They can't -- If the driver for Transmeta CPUs is loaded,
cpufreq governors cannot be started.
> You may want to make the sampling rate configurable at run time.
Such a "tweaking by sysfs" patch can be added later.
Dominik
prev parent reply other threads:[~2003-10-21 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 17:12 [PATCH] 3/3 Dynamic cpufreq governor and updates to ACPI P-statedriver Moore, Robert
2003-10-21 20:01 ` Dominik Brodowski [this message]
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=20031021200114.GB26971@brodo.de \
--to=linux@brodo.de \
--cc=andrew.grover@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=cpufreq@www.linux.org.uk \
--cc=guy.therien@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-acpi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=venkatesh.pallipadi@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