public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Homann <fexpop-53koH/AXb86i2/dY4+mD5w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Dominik Brodowski
	<linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@public.gmane.org>
Subject: Re: Centrino not scaling to lowest frequency
Date: Thu, 25 Aug 2005 17:04:50 +0200	[thread overview]
Message-ID: <200508251704.50673.fexpop@onlinehome.de> (raw)
In-Reply-To: <20050824105002.GC12792-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>

On Wednesday 24 August 2005 12:50, Dominik Brodowski wrote:
> That's because other Operating Systems do "throttling" on top of "CPU
> frequency scaling", even though that doesn't save you any energy. The
> better energy usage rates of Windows are a known problem; hopefully the
> dynamic tick patch will improve the situation in this regard.
>
> 	Dominik
>

Thanks for the info. The dynamic tick patch sounds really interesting! I'll 
give it a try.

BTW, Intel's CPU identifiction utility reports a system bus frequency of 400 
MHz when the CPU is reported to work at 600 MHz. Usually the system bus is 
running at 533 MHz. Is this the effect of "throttling" on top of "CPU 
frequency scaling" or is this something different?

Thanks,

Felix


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-08-25 15:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 21:44 Centrino not scaling to lowest frequency Felix Homann
     [not found] ` <200508152344.11572.fexpop-53koH/AXb86i2/dY4+mD5w@public.gmane.org>
2005-08-16  8:06   ` Dominik Brodowski
     [not found]     ` <20050816080625.GE9150-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2005-08-18 16:47       ` Felix Homann
     [not found]         ` <200508181847.48291.fexpop-53koH/AXb86i2/dY4+mD5w@public.gmane.org>
2005-08-19  3:55           ` Ow Mun Heng
     [not found]             ` <1124423704.8620.25.camel-/ZsuMndpQpsb5wn6fCfWY+TW4wlIGRCZ@public.gmane.org>
2005-08-25 14:09               ` Andrew Haninger
2005-08-24 10:50           ` Dominik Brodowski
     [not found]             ` <20050824105002.GC12792-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2005-08-25 13:57               ` Ow Mun Heng
     [not found]                 ` <1124978274.16010.0.camel-/ZsuMndpQpsb5wn6fCfWY+TW4wlIGRCZ@public.gmane.org>
2005-08-25 14:04                   ` Dominik Brodowski
     [not found]                     ` <20050825140456.GA8630-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2005-08-25 14:20                       ` Ow Mun Heng
     [not found]                         ` <1124979626.16010.3.camel-/ZsuMndpQpsb5wn6fCfWY+TW4wlIGRCZ@public.gmane.org>
2005-08-25 15:00                           ` Felix Homann
2005-09-02 13:09                       ` Erik Slagter
2005-08-25 15:04               ` Felix Homann [this message]
     [not found]                 ` <200508251704.50673.fexpop-53koH/AXb86i2/dY4+mD5w@public.gmane.org>
2005-08-25 15:37                   ` Dominik Brodowski
     [not found]                     ` <20050825153703.GA594-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2005-08-25 17:30                       ` Felix Homann
2005-08-16  8:44   ` Johan Vromans
     [not found]     ` <m2u0hqqni1.fsf-KjnUIgV0B0bak1Ioo/c9IoRWq/SkRNHw@public.gmane.org>
2005-08-16  9:28       ` Felix Homann
     [not found]         ` <200508161128.20966.fexpop-53koH/AXb86i2/dY4+mD5w@public.gmane.org>
2005-08-16 11:53           ` Johan Vromans

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=200508251704.50673.fexpop@onlinehome.de \
    --to=fexpop-53koh/axb86i2/dy4+md5w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@public.gmane.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