cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Jeroen Van der Vegt <A.J.vanderVegt@its.tudelft.nl>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Userspace: available processorspeeds
Date: Mon, 6 Oct 2003 20:59:38 +0100	[thread overview]
Message-ID: <20031006195938.GB1621@redhat.com> (raw)
In-Reply-To: <3F81339D.6010305@ITS.TUDelft.nl>

On Mon, Oct 06, 2003 at 11:19:25AM +0200, Jeroen Van der Vegt wrote:

 > Besides this, I have experienced the following weirdness: according to 
 > /sys/.../scaling_min_freq, my processor's minimum speed is 532 Mhz. I 
 > have, however, had it running at 292Mhz (as reported by /proc/cpuinfo). 

The 532 is a calculated speed using FSB speed * a multipler.
The 292 is an estimate based upon bogomips calculation at boot time,
and also, is subject to thermal throttling by ACPI if present.

Think of '532' as actual speed, and '292' as effective speed.

		Dave

-- 
 Dave Jones     http://www.codemonkey.org.uk

      parent reply	other threads:[~2003-10-06 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06  9:19 Userspace: available processorspeeds Jeroen Van der Vegt
2003-10-06 12:38 ` Ducrot Bruno
2003-10-06 19:59 ` Dave Jones [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=20031006195938.GB1621@redhat.com \
    --to=davej@redhat.com \
    --cc=A.J.vanderVegt@its.tudelft.nl \
    --cc=cpufreq@www.linux.org.uk \
    /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