From: akpm@osdl.org
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, ak@suse.de
Subject: [patch 088/198] x86_64: Correct wrong comment in local.h
Date: Tue, 12 Apr 2005 03:31:55 -0700 [thread overview]
Message-ID: <200504121032.j3CAW2Bk005479@shell0.pdx.osdl.net> (raw)
From: "Andi Kleen" <ak@suse.de>
local_t is actually a win over atomic_t because it does not need lock
prefixes.
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
---
25-akpm/include/asm-x86_64/local.h | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
diff -puN include/asm-x86_64/local.h~x86_64-correct-wrong-comment-in-localh include/asm-x86_64/local.h
--- 25/include/asm-x86_64/local.h~x86_64-correct-wrong-comment-in-localh 2005-04-12 03:21:24.242451488 -0700
+++ 25-akpm/include/asm-x86_64/local.h 2005-04-12 03:21:24.245451032 -0700
@@ -45,7 +45,8 @@ static __inline__ void local_sub(unsigne
:"ir" (i), "m" (v->counter));
}
-/* On x86, these are no better than the atomic variants. */
+/* On x86-64 these are better than the atomic variants on SMP kernels
+ because they dont use a lock prefix. */
#define __local_inc(l) local_inc(l)
#define __local_dec(l) local_dec(l)
#define __local_add(i,l) local_add((i),(l))
_
reply other threads:[~2005-04-13 3:19 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=200504121032.j3CAW2Bk005479@shell0.pdx.osdl.net \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®