From: Arjan van de Ven <arjan@infradead.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: S K <nospamnoham@gmail.com>, Zhao Yakui <yakui.zhao@intel.com>,
Thomas Renninger <trenn@suse.de>,
Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: cpufreq doesn't seem to work in Intel Q9300
Date: Mon, 11 Aug 2008 09:20:47 -0700 [thread overview]
Message-ID: <20080811092047.42bf716b@infradead.org> (raw)
In-Reply-To: <20080811160346.GB21292@cs181140183.pp.htv.fi>
On Mon, 11 Aug 2008 19:03:46 +0300
Adrian Bunk <bunk@kernel.org> wrote:
> On Mon, Aug 11, 2008 at 07:11:28AM -0700, Arjan van de Ven wrote:
> >...
> > so before you had for one second "20% expensive, 80% low power"
> > now you have for one second "20% expensive, 20% throttle power, 60%
> > low power"
> >
> > since throttle power is higher than low/idle power.. you lose.
>
> So what is the intended use case?
>
it's thermal throttling.
To forcefully reduce the number of cycles that have the full "execute"
power in order to clamp the temperature if the cpu is too hot.
>
> There must be a reason why Intels CPUs support this throttling?
yes there is.. for cases where there is overtemperature. Think of it as
the emergency break in the subway. You really don't want to use it but
when you need it you're glad it's there.
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-08-11 16:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <514e099a0808030300u140a0ae7m92a2e7294f39f7b7@mail.gmail.com>
2008-08-03 10:31 ` cpufreq doesn't seem to work in Intel Q9300 none
2008-08-04 5:06 ` S K
2008-08-07 9:35 ` S K
2008-08-07 19:24 ` Alan Jenkins
2008-08-08 1:32 ` Zhao Yakui
2008-08-08 4:53 ` S K
2008-08-08 8:41 ` Alan Jenkins
2008-08-08 10:10 ` S K
2008-08-08 10:43 ` S K
2008-08-08 12:30 ` Thomas Renninger
2008-08-08 18:23 ` S K
2008-08-09 18:59 ` Thomas Renninger
2008-08-09 19:30 ` Thomas Renninger
2008-08-10 8:28 ` S K
2008-08-11 1:33 ` Zhao Yakui
2008-08-11 4:44 ` S K
2008-08-11 5:24 ` Zhao Yakui
2008-08-11 5:24 ` S K
2008-08-11 7:00 ` Alan Cox
2008-08-11 10:55 ` Andi Kleen
2008-08-11 13:15 ` S K
2008-08-11 13:23 ` Andi Kleen
2008-08-12 5:43 ` S K
2008-08-11 11:22 ` Arjan van de Ven
2008-08-11 11:38 ` Alexey Dobriyan
2008-08-11 11:53 ` Matthew Garrett
2008-08-11 14:02 ` Adrian Bunk
2008-08-11 14:07 ` Matthew Garrett
2008-08-11 14:12 ` Arjan van de Ven
2008-08-11 14:11 ` Arjan van de Ven
2008-08-11 16:03 ` Adrian Bunk
2008-08-11 16:20 ` Arjan van de Ven [this message]
2008-08-11 16:28 ` Adrian Bunk
2008-08-11 16:44 ` Arjan van de Ven
2008-08-12 19:27 ` Adrian Bunk
2008-08-11 19:33 ` Dominik Brodowski
2008-08-11 23:58 ` Arjan van de Ven
2008-08-12 19:03 ` Dominik Brodowski
2008-08-12 19:59 ` Arjan van de Ven
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=20080811092047.42bf716b@infradead.org \
--to=arjan@infradead.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=bunk@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nospamnoham@gmail.com \
--cc=trenn@suse.de \
--cc=yakui.zhao@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