From: Sebastian Siewior <sebastian@breakpoint.cc>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@suse.de>
Subject: [patch 2/2] x86_64: use asm() like the other atomic operations already do.
Date: Wed, 15 Aug 2007 00:38:47 +0200 [thread overview]
Message-ID: <20070814224337.637361487@breakpoint.cc> (raw)
In-Reply-To: 20070814223845.518697567@breakpoint.cc
[-- Attachment #1: atomic_x86_64.diff --]
[-- Type: text/plain, Size: 2707 bytes --]
As Segher pointed out, inline asm is better than the volatile casting all over
the place. From the PowerPC patch description:
Also use inline functions instead of macros; this actually
improves code generation (some code becomes a little smaller,
probably because of improved alias information -- just a few
hundred bytes total on a default kernel build, nothing shocking).
My config with march=k8 and gcc (GCC) 4.1.2 (Gentoo 4.1.2):
text data bss dec hex filename
4002473 385936 474440 4862849 4a3381 atomic_normal/vmlinux
4002587 385936 474440 4862963 4a33f3 atomic_inlineasm/vmlinux
4003911 385936 474440 4864287 4a391f atomic_volatile/vmlinux
4003959 385936 474440 4864335 4a394f atomic_volatile_inline/vmlinux
Signed-off-by: Sebastian Siewior <sebastian@breakpoint.cc>
--- a/include/asm-x86_64/atomic.h
+++ b/include/asm-x86_64/atomic.h
@@ -29,19 +29,34 @@ typedef struct { int counter; } atomic_t
/**
* atomic_read - read atomic variable
* @v: pointer of type atomic_t
- *
+ *
* Atomically reads the value of @v.
- */
-#define atomic_read(v) ((v)->counter)
+ */
+static __inline__ int atomic_read(const atomic_t *v)
+{
+ int t;
+
+ __asm__ __volatile__(
+ "movl %1, %0"
+ : "=r"(t)
+ : "m"(v->counter));
+ return t;
+}
/**
* atomic_set - set atomic variable
* @v: pointer of type atomic_t
* @i: required value
- *
+ *
* Atomically sets the value of @v to @i.
- */
-#define atomic_set(v,i) (((v)->counter) = (i))
+ */
+static __inline__ void atomic_set(atomic_t *v, int i)
+{
+ __asm__ __volatile__(
+ "movl %1, %0"
+ : "=m"(v->counter)
+ : "ir"(i));
+}
/**
* atomic_add - add integer to atomic variable
@@ -206,7 +221,7 @@ static __inline__ int atomic_sub_return(
/* An 64bit atomic type */
-typedef struct { volatile long counter; } atomic64_t;
+typedef struct { long counter; } atomic64_t;
#define ATOMIC64_INIT(i) { (i) }
@@ -217,7 +232,16 @@ typedef struct { volatile long counter;
* Atomically reads the value of @v.
* Doesn't imply a read memory barrier.
*/
-#define atomic64_read(v) ((v)->counter)
+static __inline__ long atomic64_read(const atomic64_t *v)
+{
+ long t;
+
+ __asm__ __volatile__(
+ "movq %1, %0"
+ : "=r"(t)
+ : "m"(v->counter));
+ return t;
+}
/**
* atomic64_set - set atomic64 variable
@@ -226,7 +250,13 @@ typedef struct { volatile long counter;
*
* Atomically sets the value of @v to @i.
*/
-#define atomic64_set(v,i) (((v)->counter) = (i))
+static __inline__ void atomic64_set(atomic64_t *v, long i)
+{
+ __asm__ __volatile__(
+ "movq %1, %0"
+ : "=m"(v->counter)
+ : "ir"(i));
+}
/**
* atomic64_add - add integer to atomic64 variable
--
next prev parent reply other threads:[~2007-08-14 22:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 22:38 [patch 0/2] use asm() for atomic_{read|set} Sebastian Siewior
2007-08-14 22:38 ` [patch 1/2] i386: use asm() like the other atomic operations already do Sebastian Siewior
2007-08-15 0:20 ` Andi Kleen
2007-08-15 7:04 ` Sebastian Siewior
2007-08-15 8:40 ` Herbert Xu
2007-08-15 13:02 ` Satyam Sharma
2007-08-15 13:45 ` Sebastian Siewior
2007-08-15 17:02 ` Chris Snook
2007-08-15 23:44 ` Herbert Xu
2007-08-16 1:37 ` Nick Piggin
2007-08-16 19:23 ` Chris Snook
2007-08-17 0:04 ` Herbert Xu
2007-08-14 22:38 ` Sebastian Siewior [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-15 20:54 [patch 0/2] use asm() for atomic_{read|set} (shot 2) Sebastian Siewior
2007-08-15 20:54 ` [patch 2/2] x86_64: use asm() like the other atomic operations already do Sebastian Siewior
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=20070814224337.637361487@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=ak@suse.de \
--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