All of lore.kernel.org
 help / color / mirror / Atom feed
From: Forest Bond <forest@alittletooquiet.net>
To: Dave Jones <davej@redhat.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: acpi-cpufreq; Intel Johnstown (Atom N270)
Date: Thu, 13 Aug 2009 15:09:02 -0400	[thread overview]
Message-ID: <20090813190902.GD9385@alittletooquiet.net> (raw)
In-Reply-To: <20090813190741.GA7808@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

Hi,

On Thu, Aug 13, 2009 at 03:07:41PM -0400, Dave Jones wrote:
> On Thu, Aug 13, 2009 at 02:29:08PM -0400, Forest Bond wrote:
>  > Hi,
>  > 
>  > On Thu, Aug 13, 2009 at 01:25:57PM -0400, Forest Bond wrote:
>  > > I'm using an Intel Johnstown board with an Atom N270 processor.  Performance
>  > > seems to improve dramatically with acpi-cpufreq loaded.  This caught me by
>  > > surprise.  I had assumed that without loading acpi-cpufreq the CPU would be
>  > > running at its maximum speed all the time.
>  > 
>  > I ran some tests to get some numbers.  My findings indicate that before
>  > acpi-cpufreq is loaded the CPU is running at 800MHz even though /proc/cpuinfo
>  > indicates 1.6GHz.
> 
> if no cpufreq modules have been loaded, the CPU will be running at whatever
> p-state the BIOS programmed it to start up at. In your case for some reason, that's
> the 'slow' speed. 

Okay, that's what I figured.

Looks like there's some BIOS settings that may have an effect.  I'll play with
those.

Thanks,
Forest
-- 
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2009-08-13 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 17:25 acpi-cpufreq; Intel Johnstown (Atom N270) Forest Bond
2009-08-13 18:29 ` Forest Bond
2009-08-13 19:07   ` Dave Jones
2009-08-13 19:09     ` Forest Bond [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=20090813190902.GD9385@alittletooquiet.net \
    --to=forest@alittletooquiet.net \
    --cc=davej@redhat.com \
    --cc=linux-acpi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.