public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick McFarland <diablod3@gmail.com>
To: "Miles Lane" <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: The ondemand CPUFreq code -- I hope the functionality stays
Date: Thu, 27 Jul 2006 21:04:23 -0400	[thread overview]
Message-ID: <200607272104.24088.diablod3@gmail.com> (raw)
In-Reply-To: <a44ae5cd0607270154p50c2c7fcx734bfea026dc69a9@mail.gmail.com>

On Thursday 27 July 2006 04:54, Miles Lane wrote:
> Hello,
>
> It sounds, from comments in the discussion of CPU Hotplug locking
> problems, as though you are considering deleting the ondemand CPUFreq
> code.  If this happens, I hope that something that provides the same
> functionality replaces it.  I really appreciate having my power
> consumption automatically modulated on an as needed basis.  Power
> management seems to be one of the areas where there is a lot of room
> for improvement.

I think you've gotten confused. Ondemand is a horrible governor that only 
flips between two cpu frequencies, the lowest and the highest. Use the 
Conservative governor instead.

Also, the locking issues have nothing to do with Ondemand, its just that 
Ondemand's suckyness came up in the thread.

> Thanks,
>       Miles

-- 
Patrick McFarland || www.AdTerrasPerAspera.com
"Computer games don't affect kids; I mean if Pac-Man affected us as kids,
we'd all be running around in darkened rooms, munching magic pills and
listening to repetitive electronic music." -- Kristian Wilson, Nintendo,
Inc, 1989


  parent reply	other threads:[~2006-07-28  1:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27  8:54 The ondemand CPUFreq code -- I hope the functionality stays Miles Lane
2006-07-27 10:12 ` Arjan van de Ven
2006-07-28  1:04 ` Patrick McFarland [this message]
2006-07-28  1:10   ` Dave Jones
2006-07-28  1:25     ` Patrick McFarland
2006-07-28 10:38     ` Miles Lane
2006-07-28  2:43   ` Thomas Tuttle
2006-07-28  9:24     ` Arjan van de Ven

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=200607272104.24088.diablod3@gmail.com \
    --to=diablod3@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles.lane@gmail.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