From: Dominik Brodowski <linux@brodo.de>
To: "Måns Rullgård" <mru@kth.se>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver
Date: Tue, 21 Oct 2003 22:47:19 +0200 [thread overview]
Message-ID: <20031021204719.GI26971@brodo.de> (raw)
In-Reply-To: <yw1xoewb6lqx.fsf@kth.se>
On Tue, Oct 21, 2003 at 10:25:10AM +0200, Måns Rullgård wrote:
> "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> writes:
>
> > Most of the latest CPUs (laptop CPUs in particular) have feature
> > which enable very low latency P-state transitions
> > (like Enhanced Speedstep Technology-EST). Using this feature,
> > we can have a lightweight in kernel cpufreq governor,
> > to vary CPU frequency depending on the CPU usage. The
> > advantage being low power consumption and also cooler laptops.
>
> So, how does this work? I'd like to be able to set minimum and
> maximum clock frequencies to allow
echo "..." > /sys/devices/system/cpu/0/cpufreq/scaling_min_speed
echo "..." > /sys/devices/system/cpu/0/cpufreq/scaling_max_speed
>, and CPU utilization thresholds at which to switch frequencies.
select the demandbased governor
echo "demandbased" > /sys/devices/system/cpu/0/cpufreq/scaling_governor
and wait for the inclusion of a sysfs interface to the demandbased governor
which lets you override the current switching frequencies of 20% and 80%.
> Is that possible, or is it work yet to be done?
Almost done.
> Adjustable polling interval would also be nice.
Should also be adaptable by sysfs. This sysfs interface really will be a
very useful addition, but it's not top priority.
Dominik
next prev parent reply other threads:[~2003-10-21 20:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 2:56 [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver Pallipadi, Venkatesh
2003-10-21 8:25 ` Måns Rullgård
2003-10-21 20:47 ` Dominik Brodowski [this message]
2003-10-21 10:57 ` Måns Rullgård
2003-10-21 11:09 ` Måns Rullgård
2003-10-21 20:30 ` Alexander Bokovoy
2003-10-21 20:39 ` Måns Rullgård
2003-10-21 21:11 ` Alexander Bokovoy
2003-10-21 21:37 ` Måns Rullgård
2003-10-21 21:53 ` Alexander Bokovoy
2003-10-21 22:27 ` Måns Rullgård
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 1:42 Pallipadi, Venkatesh
2003-10-22 1:48 Pallipadi, Venkatesh
2003-10-22 18:21 Pallipadi, Venkatesh
2003-10-23 8:19 ` Arjan van de Ven
2003-10-23 8:24 ` Alexander Bokovoy
2003-10-23 8:29 ` Arjan van de Ven
2003-10-23 18:03 ` Ducrot Bruno
2003-10-23 18:16 ` Todd Poynor
2003-10-23 18:26 ` Todd Poynor
2003-11-02 20:28 ` Jan Rychter
2003-11-04 3:14 Brown, Len
2003-11-04 3:21 ` Jan Rychter
2003-11-04 7:16 ` Dominik Brodowski
2003-11-05 21:12 Mukesh Rajan
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=20031021204719.GI26971@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
--cc=mru@kth.se \
/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