public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig Brady <padraig.brady@corvil.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Cort Dougan <cort@fsmlabs.com>,
	Dominik Brodowski <devel@brodo.de>,
	cpufreq@www.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5.32] CPU frequency and voltage scaling (0/4)
Date: Thu, 29 Aug 2002 10:51:34 +0100	[thread overview]
Message-ID: <3D6DEEA6.1010400@corvil.com> (raw)
In-Reply-To: Pine.LNX.4.33.0208281249520.4507-100000@penguin.transmeta.com

Linus Torvalds wrote:
> On 28 Aug 2002, Alan Cox wrote:
> 
>>Systems designers are designing on the basis of thermal slowdowns being
>>the optimal way to build some systems. Its actually quite reasonable for
>>many workloads.
> 
> Absolutely. Thermal policy is often an overriding thing, where even 
> non-transmeta CPU's will simply do the decision "on their own", without 
> input from the OS. That's simply because some designs will literally not 
> work above certain temperatures and do not have the heat sink capacity to 
> get out of a tight spot by purely external cooling. 
> 
> But that's just one part of it. Even aside from thermal concerns, you want 
> to drop frequency aggressively when the machine is idle, because dropping 
> the frequency allows you to drop the voltage and effetively gets you a 
> cubed power reduction (which not only saves your battery, but also cools 
> the chip down so that when you _do_ start going full speed again you have 
> more thermal headroom).
> 
> So in order to avoid the thermal shutdown, you need to be proactive about 
> the frequency. Which again means that a user-level "once a second" or 
> "once in a blue moon" approach is fundamentally flawed.

Just a data point from my application. First of all with VIA CPUs
there is a 1ms delay per change when it resyncs things, so it's
not practical to do it very often or for realtime apps etc.
My application was purely a heat reduction exercise where the
timescale from 0°C to 70°C was around 10 minutes at max voltage/frequency,
so it could easily be controlled by a userspace application.
In fact I didn't control it manually and only set the frequency
(for which the appropriate voltage was chosen by the cpufreq code)
at system startup.

> I don't disagree with _also_ being able to set the frequency statically. 
> However, I do disagree with an interface that seems to be _purely_ 
> designed for this, and nothing else. 
> 
> 		Linus

Pádraig.


  reply	other threads:[~2002-08-29  9:48 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 11:46 [PATCH][2.5.32] CPU frequency and voltage scaling (0/4) Dominik Brodowski
2002-08-28 18:47 ` Linus Torvalds
2002-08-28 18:48   ` Cort Dougan
2002-08-28 19:25     ` Alan Cox
2002-08-28 19:32       ` Cort Dougan
2002-08-29 10:26         ` Zwane Mwaikambo
2002-08-28 19:41       ` Peter Riocreux
2002-08-28 19:58       ` Linus Torvalds
2002-08-29  9:51         ` Padraig Brady [this message]
2002-08-29 10:23     ` Zwane Mwaikambo
2002-08-28 19:21   ` Alan Cox
2002-08-28 19:49     ` Linus Torvalds
2002-08-28 20:25       ` Alan Cox
2002-08-28 20:29         ` Linus Torvalds
2002-08-28 23:26           ` Alan Cox
2002-08-28 23:49             ` Linus Torvalds
2002-08-30  0:39               ` jw schultz
2002-08-29  7:01             ` Dominik Brodowski
2002-08-28 20:39         ` Dominik Brodowski
2002-08-28 21:05           ` Linus Torvalds
2002-09-06 11:31             ` Pavel Machek
2002-08-28 20:27       ` Dominik Brodowski
2002-08-28 20:19   ` Dominik Brodowski
2002-08-28 20:43     ` Linus Torvalds
2002-08-28 20:53       ` Dominik Brodowski
2002-08-28 21:08         ` Linus Torvalds
2002-08-28 23:00           ` george anzinger
2002-08-28 23:30           ` Alan Cox
2002-08-29  0:08             ` Linus Torvalds
2002-08-29  7:07               ` Dominik Brodowski
2002-08-29 10:02               ` Padraig Brady
2002-08-29 10:53               ` Alan Cox
2002-08-29 13:38                 ` Dave Jones
2002-08-29 18:47                 ` Linus Torvalds
2002-08-29 19:24                   ` Alan Cox
2002-08-29 21:22                   ` george anzinger
2002-08-30  6:46                     ` David Gibson
2002-08-30  7:54                     ` Helge Hafting
2002-08-30  3:21                 ` David Lang
  -- strict thread matches above, loose matches on Subject: below --
2002-08-28 20:25 Grover, Andrew
2002-08-28 20:46 ` Linus Torvalds
2002-08-29 15:07 Pering, Trevor
2002-08-30  8:04 ` Helge Hafting
2002-08-30 11:53   ` Dave Jones
2002-08-30 12:36     ` Helge Hafting
2002-08-30 22:43       ` george anzinger

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=3D6DEEA6.1010400@corvil.com \
    --to=padraig.brady@corvil.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cort@fsmlabs.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=devel@brodo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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