From: Simon Kirby <sim@stormix.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Pentium 4 and 2.4/2.5
Date: Thu, 9 Nov 2000 15:42:44 -0500 [thread overview]
Message-ID: <20001109154243.A25865@stormix.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1001108132530.8587A-100000@kanga.kvack.org> <E13taG6-0000JH-00@the-village.bc.nu>
In-Reply-To: <E13taG6-0000JH-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Nov 08, 2000 at 06:47:40PM +0000
On Wed, Nov 08, 2000 at 06:47:40PM +0000, Alan Cox wrote:
> Ok. Issue settled. So 'rep nop' is safe. Ok that can get into the spinlocks
> for 2.2.18
Just curious... What does "rep nop" actually accomplish, anyway?
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
-
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/
next prev parent reply other threads:[~2000-11-09 20:43 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
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 [this message]
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=20001109154243.A25865@stormix.com \
--to=sim@stormix.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