public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question about cpufreq governors
Date: Sat, 7 Jul 2007 12:04:08 +0200	[thread overview]
Message-ID: <20070707100408.GA19299@DervishD> (raw)
In-Reply-To: <Pine.LNX.4.64.0707062353510.1536@fbirervta.pbzchgretzou.qr>

    Hi Jan :)

 * Jan Engelhardt <jengelh@computergmbh.de> dixit:
> 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).

    Yes, I know the difference, I'm afraid I didn't ask my question
correctly O:). What I meant is that, since I don't know if my CPU has
latency problems when switching from "slow" freq to "fast" freq, if I
can use "ondemand" safely or if I must use "conservative" due to latency
problems with my CPU.

    Thanks for your answer :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

      parent reply	other threads:[~2007-07-07 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 20:50 Question about cpufreq governors DervishD
2007-07-06 21:54 ` Jan Engelhardt
2007-07-06 22:50   ` Arjan van de Ven
2007-07-07 10:06     ` DervishD
2007-07-07 10:04   ` DervishD [this message]

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=20070707100408.GA19299@DervishD \
    --to=lkml@dervishd.net \
    --cc=jengelh@computergmbh.de \
    --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