From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: "Calin A. Culianu" <calin@ajvar.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: SMP Pentium4 -- PAUSE Instruction
Date: Tue, 3 Dec 2002 07:57:09 -0800 [thread overview]
Message-ID: <F2DBA543B89AD51184B600508B68D4001070ED28@fmsmsx103.fm.intel.com> (raw)
That one is for tight loops. Spin locks are inlined, and PAUSE is used like:
#define spin_lock_string \
"\n1:\t" \
"lock ; decb %0\n\t" \
"js 2f\n" \
LOCK_SECTION_START("") \
"2:\t" \
"cmpb $0,%0\n\t" \
"rep;nop\n\t" \ <---
"jle 2b\n\t" \
"jmp 1b\n" \
LOCK_SECTION_END
Also take a look at arch/i386/kernel/semaphore.c for read/write_locks.
Jun
> -----Original Message-----
> From: Calin A. Culianu [mailto:calin@ajvar.org]
> Sent: Tuesday, December 03, 2002 7:42 AM
> To: Linux Kernel Mailing List
> Subject: SMP Pentium4 -- PAUSE Instruction
>
>
> I as wondering -- according to Intel's docs they recommend that on a P4
> processor to use the PAUSE instruction (aka rep followed by a nop) inside
> any spin loop (such as one used in SMP spinlock code) in order to both
> improve processor performance and reduce power consumption.
>
> Is this instruction being used in spin-wait loops? For some reason, I am
> having a hard time figuring out whether or not it is being used. There is
> a rep_nop() in processor.h.. but I can't determine if that is being called
> for spin lock lock/unlock code.
>
>
> -Calin
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2002-12-03 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 15:57 Nakajima, Jun [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 15:42 Calin A. Culianu
2002-12-03 15:55 ` Dave Jones
2002-12-03 16:06 ` Arjan van de Ven
2002-12-03 17:21 ` Calin A. Culianu
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=F2DBA543B89AD51184B600508B68D4001070ED28@fmsmsx103.fm.intel.com \
--to=jun.nakajima@intel.com \
--cc=calin@ajvar.org \
--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
all inboxes | Powered by JetHome®