From: Ian Romanick <idr@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC/SERIOUS] grilling troubled CPUs for fun and profit?
Date: Wed, 21 Jun 2006 10:16:32 -0700 [thread overview]
Message-ID: <44997EF0.3000005@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0606200729280.7695@chaos.analogic.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
linux-os (Dick Johnson) wrote:
> The CPU produces heat. It's efficiency as a heater is nearly 100%
> because it doesn't produce much noise or anything else to transfer
> its 50+ watts into anything but heat. Spinning doesn't make friction.
> It doesn't make more heat. The total box dissipation might even
> be reduced because there is little memory activity and no seeks
> of hard disks.
>
> Some CPUs will go to a low-power 'sleep' mode if halted. Some require
> more than that, they must fetch 'pause', i.e., rep nop to stay in
> a low power mode. Other CPUs will throttle back their power
> consumption when the instruction cache is inactive, read spinning.
> These CPUs are normally used in lap-tops to maximize battery life.
What creates a fair amount of the heat in a CPU is the period of time
when the transistors switch from nearly zero resistance to infinite
resistance. That brief period where the resistance very high but not
yet infinite generates heat. That's why running a CPU at a higher clock
speed generates more heat: there are more of those high resistance
transitions in a given period of time.
I think every processor since at least 1998 or so has had a mode where
executing the HLT instruction puts the bulk of the chip in a steady
state. When it's in that steady state, the transistors don't switch, so
there are no high resistance periods.
This is, of course, completely different than the sleep or reduced clock
modes that modern processors support.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEmX7wX1gOwKyEAw8RAu+MAJwOgq1rwrcr+dQHnM9ucT6R1+ZlOACgkLR7
J0CmccUthcHknCaXYTL6ON0=
=lkld
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-06-21 17:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 19:15 [RFC/SERIOUS] grilling troubled CPUs for fun and profit? Andreas Mohr
2006-06-19 19:39 ` John Richard Moser
2006-06-19 20:00 ` linux-os (Dick Johnson)
2006-06-19 20:23 ` Dave Jones
2006-06-19 20:47 ` linux-os (Dick Johnson)
2006-06-19 20:59 ` Dave Jones
2006-06-19 22:25 ` Pavel Machek
2006-06-19 22:41 ` Dave Jones
2006-06-20 11:39 ` linux-os (Dick Johnson)
2006-06-21 17:16 ` Ian Romanick [this message]
2006-06-21 17:57 ` linux-os (Dick Johnson)
2006-06-22 17:47 ` Pavel Machek
2006-06-20 9:58 ` Jan Engelhardt
2006-06-22 18:16 ` Pavel Machek
2006-06-23 17:32 ` Jan Engelhardt
2006-06-24 19:54 ` Pavel Machek
2006-06-25 11:01 ` Jan Engelhardt
2006-06-20 9:54 ` Jan Engelhardt
2006-06-19 21:16 ` Claudio Martins
2006-06-19 22:16 ` Pavel Machek
2006-06-19 22:43 ` Dave Jones
2006-06-20 7:29 ` Andreas Mohr
[not found] <6pxs2-1AR-5@gated-at.bofh.it>
[not found] ` <6pyer-2Pt-1@gated-at.bofh.it>
2006-06-19 21:40 ` Bodo Eggert
2006-06-19 21:44 ` Dave Jones
[not found] <fa.pC0NfRl4O1eOCqPOBXy8f+7gbqU@ifi.uio.no>
[not found] ` <fa.so5wrYE6MzA2swzlOE1Xjw9iqvk@ifi.uio.no>
2006-06-19 23:32 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 3:30 Ken Ryan
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=44997EF0.3000005@us.ibm.com \
--to=idr@us.ibm.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox