public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: dual_bereta_r0x <dual_bereta_r0x@arenanetwork.com.br>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: linux-kernel@vger.kernel.org, cpufreq@www.linux.org.uk
Subject: Re: 2.6.2: P4 ClockMod speed
Date: Mon, 16 Feb 2004 21:48:25 +0000	[thread overview]
Message-ID: <40313AA9.1060906@arenanetwork.com.br> (raw)
In-Reply-To: <20040216213435.GA9680@dominikbrodowski.de>

Dominik Brodowski wrote:
> Hi,
> 
> 
>>I have a P4 2.4 running @ 3.12GHz.
> 
> 
> So you overclock your CPU but then throttle it down... strange, but well...

Actually it isn't throttled down, only sysfs is showing it with low 
speed. It *is* running @ 3.12 (or /proc/cpuinfo and boot messages are 
lying to me) when in full power.

>>In 2.6.0, i could change it frequency 
>>via speedfreqd(8) up to its actual speed. Since 2.6.1, its max speed is 
>>locked on cpu *real* speed.
> 
> 
> It's just a change of appearance -- the cpufreq driver uses the theoretical
> speed of the CPU for its calculations; the actual CPU speed isn't
> affected. You can verify this by looking at /proc/cpuinfo which still tells
> 3124.376 MHz.
> 
> By doing so it becomes easier to enter different frequencies e.g. into
> /sys/devices/system/cpu/cpufreq/scaling_setspeed -- on my desktop, typing in
> 1200000 is easier than 12121224... [*]

Sure but if i want to downgrade it, for example, by night, to a lower 
speed, and then next day return it to full power? Will I stuck at 2.4GHz?

> 	Dominik
> 
> [*] The _actual_ CPU speed should be used on all cpufreq drivers where this
> specific CPU frequency has implications to external components, e.g. LCD,
> memory or pcmcia devices. Where only the _frequency ratio_ is of importance
> [for loops_per_jiffy and friends] such "rounding" is acceptable, as long as
> the ratio is constant.

Indeed. I'll showing in LCD a lower speed than the running.

-- 
dual_bereta_r0x -- Alexandre Hautequest
ArenaNetwork Lan House & Cyber -- www.arenanetwork.com.br

Três anéis para os Reis Élficos sob este céu,
    Sete para os Senhores-Anões em seus rochosos corredores,
Nove para Homens Mortais, fadados ao eternos sono,
    Um para o Senhor do Escuro em seu escuro trono
Na Terra de Mordor onde as Sombras se deitam.
    Um Anel para a todos governar, Um Anel para encontrá-los,
    Um Anel para a todos trazer e na escuridão aprisioná-los
Na Terra de Mordor onde as Sombras se deitam.

  reply	other threads:[~2004-02-16 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 21:34 2.6.2: P4 ClockMod speed Dominik Brodowski
2004-02-16 21:48 ` dual_bereta_r0x [this message]
2004-02-16 21:57   ` Bruno Ducrot
2004-02-17  9:09   ` Dominik Brodowski
2004-02-26  1:28     ` dual_bereta_r0x
2004-03-03 19:12       ` Bruno Ducrot
2004-02-25 17:43 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-02-16 19:23 dual_bereta_r0x

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=40313AA9.1060906@arenanetwork.com.br \
    --to=dual_bereta_r0x@arenanetwork.com.br \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.de \
    /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