public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: Pentium 4 and 2.4/2.5
Date: 8 Nov 2000 09:31:24 -0800	[thread overview]
Message-ID: <8uc2lc$g4t$1@penguin.transmeta.com> (raw)
In-Reply-To: <OE59dY2pjID9Lv40q2H00001e2c@hotmail.com> <E13tGbg-0007oC-00@the-village.bc.nu>

In article <E13tGbg-0007oC-00@the-village.bc.nu>,
Alan Cox  <alan@lxorguk.ukuu.org.uk> wrote:
>
>rep;nop is a magic instruction on the PIV and possibly some PIII series CPUs
>[not sure]. As far as I can make out it naps momentarily or until bus
>activity thus saving power on spinlocks.

>From what I've heard, the reason Intel _really_ wants "rep nop" is that
without it the CPU will heat up quite efficiently (that's what you do
when you want to run at an eventual 2GHz with all cylinders firing all
the time), causing thermal meltdown on non-thermally protected CPU's and
CPU speed throttling on the ones that _are_ thermally protected (which
will obviously have to be all the shipping ones). 

And the thermal throttling will severly cripple performance.

>The problem is 'rep nop' is not defined on other cpus so we can only really use
>it on the PIII/PIV kernel builds

Intel retroactively defined it for all their CPU's. And I very strongly
suspect that every single other x86 CPU vendor does the same. Why not?
They get a new instruction for free, but just documenting it. Maybe they
can sell the same old chip with a new name ("The Xxxxx Wonderchip. Now
with documetned 'rep nop' support! Get one today!").

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-08 17:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-04 23:36 Pentium 4 and 2.4/2.5 Frank Davis
2000-11-07  3:41 ` Andre Hedrick
2000-11-07 12:13   ` Alan Cox
2000-11-07 21:06     ` Lyle Coder
2000-11-07 21:48       ` Alan Cox
2000-11-08 17:31         ` Linus Torvalds [this message]
2000-11-08 17:26     ` Linus Torvalds
2000-11-08 17:50       ` Alan Cox
2000-11-08 18:10         ` Linus Torvalds
2000-11-08 18:12           ` Brian Pomerantz
2000-11-08 18:21             ` Alan Cox
2000-11-08 18:27               ` kernel
2000-11-08 18:47                 ` Alan Cox
2000-11-09 20:42                   ` Simon Kirby
2000-11-08 18:29               ` Brian Pomerantz
2000-11-08 18:17           ` Alan Cox
2000-11-07  4:01 ` Robert M. Love
2000-11-07 12:04 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2000-11-05  0:04 Frank Davis
2000-11-08  0:43 ` Alan Cox

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='8uc2lc$g4t$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.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