linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tony Mantler <nicoya@apia.dhs.org>
To: "Timothy A. Seufert" <tas@mindspring.com>, mlan@cpu.lu, hozer@drgw.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: About TAU (and ICTC)
Date: Sun, 19 Aug 2001 15:08:46 -0500	[thread overview]
Message-ID: <v04003a08b7a5cb79017f@[24.70.162.12]> (raw)
In-Reply-To: <p05100301b7a5c073cc62@[10.0.0.42]>


At 2:51 PM -0500 8/19/2001, Timothy A. Seufert wrote:
[...]
>But if you think about it, it probably doesn't reduce the total power
>needed to do a given task.  It just spreads the power use over a
>longer period of time.  So you'll use roughly the same amount of
>energy to do one kernel compile no matter what the ICTC setting is;
>it'll just get done slower with ICTC on.
>
>In fact, because programs will generally take longer to run with ICTC
>on, I suspect that ICTC is *less* power efficient than going all-out.
>Only part of the CPU's power use is dynamic (and therefore subject to
>regulation via ICTC).  There's dielectric leakage current, which is
>constant no matter what you do, and, more importantly, plenty of
>clocked circuits which are not shut down by the dynamic power save
>circuitry.  From this one can conclude that power use per unit of
>computation done is likely higher when using ICTC.
[...]

Hmm, I wonder how much thermal-resistive factors would affect this. Y'know,
generally when a circuit is warmer, it's resistance increases, and
subsequently it gets warmer, etc, so depending on how the curves weigh out
(if at all), there might be some hidden power savings in doing calculations
cooler and longer rather than warmer and shorter.

Maybe? I dunno.


Cheers - Tony 'Nicoya' Mantler :)


--
Tony "Nicoya" Mantler - Renaissance Nerd Extraordinaire - nicoya@apia.dhs.org
Winnipeg, Manitoba, Canada           --           http://nicoya.feline.pp.se/


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-08-19 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-19 10:03 About TAU Michel Lanners
2001-08-19 15:59 ` About TAU (and ICTC) Michel Lanners
2001-08-19 19:51   ` Timothy A. Seufert
2001-08-19 20:08     ` Tony Mantler [this message]
2001-08-19 20:43       ` Geert Uytterhoeven
2001-08-19 21:23         ` Tony Mantler
2001-08-19 22:02     ` Benjamin Herrenschmidt
2001-08-19 23:57   ` Paul Mackerras

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='v04003a08b7a5cb79017f@[24.70.162.12]' \
    --to=nicoya@apia.dhs.org \
    --cc=hozer@drgw.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    --cc=tas@mindspring.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;
as well as URLs for NNTP newsgroup(s).