public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
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 10:25:10 +0200	[thread overview]
Message-ID: <yw1xoewb6lqx.fsf@kth.se> (raw)
In-Reply-To: 88056F38E9E48644A0F562A38C64FB60077911@scsmsx403.sc.intel.com

"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, and CPU utilization thresholds at
which to switch frequencies.  Is that possible, or is it work yet to
be done?  Adjustable polling interval would also be nice.

> The patches will work on all laptops with EST technology 
> (Centrino) and also on any other system that supports low 
> latency frequency change. 

Does Pentium 4 M work?

-- 
Måns Rullgård
mru@kth.se


  reply	other threads:[~2003-10-21  8:25 UTC|newest]

Thread overview: 7+ 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 [this message]
     [not found] ` <yw1xbrsaeu44.fsf@kth.se>
2003-10-21 20:30   ` Alexander Bokovoy
     [not found]     ` <yw1xoewaiavf.fsf@kth.se>
2003-10-21 21:11       ` Alexander Bokovoy
     [not found]         ` <yw1xfzhmi86r.fsf@kth.se>
2003-10-21 21:53           ` Alexander Bokovoy
  -- strict thread matches above, loose matches on Subject: below --
2003-10-22  1:42 Pallipadi, Venkatesh
2003-10-22  1:48 Pallipadi, Venkatesh

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=yw1xoewb6lqx.fsf@kth.se \
    --to=mru@kth.se \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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