From: "Miles Lane" <miles.lane@gmail.com>
To: "Dave Jones" <davej@redhat.com>,
"Patrick McFarland" <diablod3@gmail.com>,
"Miles Lane" <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: The ondemand CPUFreq code -- I hope the functionality stays
Date: Fri, 28 Jul 2006 12:38:49 +0200 [thread overview]
Message-ID: <a44ae5cd0607280338x674aa92agb49f38a494bf8923@mail.gmail.com> (raw)
In-Reply-To: <20060728011040.GO5687@redhat.com>
On 7/28/06, Dave Jones <davej@redhat.com> wrote:
> On Thu, Jul 27, 2006 at 09:04:23PM -0400, Patrick McFarland wrote:
>
> > I think you've gotten confused. Ondemand is a horrible governor that only
> > flips between two cpu frequencies, the lowest and the highest.
>
> That isn't true. I just double checked, and saw my core-duo changing
> between all 4 states it offers.
Yep, the ondemand governor switches between all frequencies on my
Pentium 4 M laptop. It's a HP Pavillion dv1240us.
> > Use the Conservative governor instead.
>
> This governor is based on the same code as on-demand with some subtle
> tweaks to make it not change the frequency as often. If anything *this*
> one should be less 'active' for you than ondemand.
I have tried the other governers (albeit a while ago) and found they
didn't manage power anywhere near as well as ondemand. Perhaps
results vary for each governor according to CPU and chipset.
Miles
next prev parent reply other threads:[~2006-07-28 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 8:54 Miles Lane
2006-07-27 10:12 ` Arjan van de Ven
2006-07-28 1:04 ` Patrick McFarland
2006-07-28 1:10 ` Dave Jones
2006-07-28 1:25 ` Patrick McFarland
2006-07-28 10:38 ` Miles Lane [this message]
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=a44ae5cd0607280338x674aa92agb49f38a494bf8923@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=davej@redhat.com \
--cc=diablod3@gmail.com \
--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
all inboxes | Powered by JetHome®