cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "Walz, Michael" <michael.walz@intel.com>, cpufreq@www.linux.org.uk
Subject: Re: Dynamic frequency governor
Date: Mon, 20 Oct 2003 16:39:37 +0100	[thread overview]
Message-ID: <20031020153936.GM2729@redhat.com> (raw)
In-Reply-To: <CFF522B18982EA4481D3A3E23B83141C24B4B0@orsmsx407.jf.intel.com>

On Mon, Oct 20, 2003 at 08:31:08AM -0700, Moore, Robert wrote:
 > 
 > I'm planning on integrating the previously released Linux IST (Intel
 > Speedstep) driver into the CpuFreq architecture.

Cool, but what does it do that the existing cpufreq speedstep drivers don't ?

 > I think that what is gained by having this code in the kernel is that a
 > very accurate measure of percent CPU utilization can be obtained
 > directly from the kernel idle handler, and there is less overhead during
 > the periodic sampling of the current CPU utilization by a timer thread.

I'm not disputing whether or not putting this in the kernel is a good
or bad thing (for the record, I think it's a good idea), however the
fact remains, whilst there are folks owning patents on this, it'll
*never* be acceptable for merging without an exception grant from the
patent holder.

		Dave


 > From: Dave Jones [mailto:davej@redhat.com] 
 > Sent: Sunday, October 19, 2003 6:24 AM
 > To: Moore, Robert
 > Cc: cpufreq@www.linux.org.uk
 > Subject: Re: Dynamic frequency governor
 > 
 > On Fri, Oct 17, 2003 at 02:14:38PM -0700, Moore, Robert wrote:
 >  
 >  > 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.
 > 
 > There are several patents in this area (I think from Hitachi, I forget
 > exactly) It has come up before on the list, so should be in the
 > archives.  Unless you can get a grant from the holder that it may be
 > used in GPL code, this has zero chance of being merged to mainline.
 > 
 > 		Dave
 > 
 > -- 
 >  Dave Jones     http://www.codemonkey.org.uk
---end quoted text---

-- 
 Dave Jones     http://www.codemonkey.org.uk

  reply	other threads:[~2003-10-20 15:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 15:31 Dynamic frequency governor Moore, Robert
2003-10-20 15:39 ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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-17 21:14 Moore, Robert
2003-10-18  5:00 ` Jeremy Fitzhardinge
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

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=20031020153936.GM2729@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=michael.walz@intel.com \
    --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