From: Manfred Spraul <manfred@colorfullife.com>
To: linux-kernel@vger.kernel.org
Subject: rep nop question
Date: Sat, 07 Apr 2001 22:41:57 +0200 [thread overview]
Message-ID: <3ACF7B95.DB4FF928@colorfullife.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
The Intel documentation recommends that spinlocks should use
loop:
rep;nop;
cmp $0,lock_var
jne loop
ftp://download.intel.com/design/perftool/cbts/appnotes/sse2/w_spinlock.pdf
but the linux spinlock implementation uses
loop:
cmp $0, lock_var
rep; nop;
jne loop.
Why?
According to the Intel documentation, rep nop is a predefined delay that
slows down the cpu to the speed of the memory bus. The linux
implementation will delay again _after_ the lock was released.
What about the attached patch? It also adds 'rep;nop' into the rw
spinlock implementation.
It boots with my Pentium III, but the cpu doesn't support 'rep nop'
(i.e. returns immediately)
--
Manfred
[-- Attachment #2: patch-rep-nop --]
[-- Type: text/plain, Size: 1013 bytes --]
// $Header$
// Kernel Version:
// VERSION = 2
// PATCHLEVEL = 4
// SUBLEVEL = 3
// EXTRAVERSION = -ac3
--- 2.4/arch/i386/kernel/semaphore.c Sun Nov 19 02:31:25 2000
+++ build-2.4/arch/i386/kernel/semaphore.c Sat Apr 7 21:26:35 2001
@@ -430,7 +430,8 @@
.globl __write_lock_failed
__write_lock_failed:
" LOCK "addl $" RW_LOCK_BIAS_STR ",(%eax)
-1: cmpl $" RW_LOCK_BIAS_STR ",(%eax)
+1: rep; nop
+ cmpl $" RW_LOCK_BIAS_STR ",(%eax)
jne 1b
" LOCK "subl $" RW_LOCK_BIAS_STR ",(%eax)
@@ -442,7 +443,8 @@
.globl __read_lock_failed
__read_lock_failed:
lock ; incl (%eax)
-1: cmpl $1,(%eax)
+1: rep; nop
+ cmpl $1,(%eax)
js 1b
lock ; decl (%eax)
--- 2.4/include/asm-i386/spinlock.h Sat Apr 7 22:02:23 2001
+++ build-2.4/include/asm-i386/spinlock.h Sat Apr 7 22:01:43 2001
@@ -58,10 +58,10 @@
"js 2f\n" \
".section .text.lock,\"ax\"\n" \
"2:\t" \
- "cmpb $0,%0\n\t" \
"rep;nop\n\t" \
- "jle 2b\n\t" \
- "jmp 1b\n" \
+ "cmpb $0,%0\n\t" \
+ "jg 1b\n\t" \
+ "jmp 2b\n" \
".previous"
/*
reply other threads:[~2001-04-08 8:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ACF7B95.DB4FF928@colorfullife.com \
--to=manfred@colorfullife.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.