From: Arjan van de Ven <arjan@infradead.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: DervishD <lkml@dervishd.net>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question about cpufreq governors
Date: Fri, 06 Jul 2007 15:50:29 -0700 [thread overview]
Message-ID: <1183762229.2774.1.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707062353510.1536@fbirervta.pbzchgretzou.qr>
On Fri, 2007-07-06 at 23:54 +0200, Jan Engelhardt wrote:
> On Jul 6 2007 22:50, DervishD wrote:
> >
> > What I want to know is if I can choose "ondemand" governor instead
> >of the recommended for AMD64, namely the "conservative" governor, since
> >I will be switching between those two frequencies. I haven't found any
> >information about my CPU regarding latency when switching between
> >frequencies, so I don't know if I will be gaining anything using the
> >"conservative" governor.
> >
> > Which governor is better suited for a CPU with only two fid's,
> >"ondemand" or "conservative"?
>
> Depends on what you want. ondemand instantly switches when there is
> something/nothing to do, while conservative uses a threshold (modeled upon
> latency).
for power saving, the ondemand behavior is better in general. However if
you have a cpu that switches frequency very slowly, you may be better to
not go as high quickly because going back down is then burning more
power than needed potentially...
next prev parent reply other threads:[~2007-07-06 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 20:50 DervishD
2007-07-06 21:54 ` Jan Engelhardt
2007-07-06 22:50 ` Arjan van de Ven [this message]
2007-07-07 10:06 ` DervishD
2007-07-07 10:04 ` DervishD
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=1183762229.2774.1.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dervishd.net \
/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®