cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mattia Dongili <malattia@gmail.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: DBS enabling on EM64T machine with cpufreqd
Date: Thu, 26 May 2005 15:36:34 +0200	[thread overview]
Message-ID: <2fc0cdd2050526063627cd16dc@mail.gmail.com> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6004D356D0@scsmsx403.amr.corp.intel.com>

On 5/26/05, Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com> wrote:
[...]
> And newer versions of the userspace governors should be able to handle
> SMP processsors. Earlier versions didn't. Not sure which version of
> cpufreqd you are using.

oh well... cpufreqd has never been able to handle the userspace governor.

[...]
> >profile=lo_power [root@ae64 cpufreq]# cpufreqd -D
> >
> >libsys_init() - no batteries found, not a laptop?
[...]

after this message cpufreqd should run correctly considering your
server always ac-on and with no battery.
Anyway, as said you're probably better using the ondemand in-kernel
governor to dinamically scale based on cpuload. You can still use
cpufreqd to apply different limits based other parameters :)

-- 
mattia
:wq!

  reply	other threads:[~2005-05-26 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 13:15 DBS enabling on EM64T machine with cpufreqd Pallipadi, Venkatesh
2005-05-26 13:36 ` Mattia Dongili [this message]
2005-06-05  1:43 ` Carl Thompson
  -- strict thread matches above, loose matches on Subject: below --
2005-05-26 10:04 Lin, Zihui

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=2fc0cdd2050526063627cd16dc@mail.gmail.com \
    --to=malattia@gmail.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=venkatesh.pallipadi@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