From: Sebastian Siewior <sebastian@breakpoint.cc>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@suse.de>, Chris Snook <csnook@redhat.com>
Subject: [patch 1/2] i386: use asm() like the other atomic operations already do.
Date: Wed, 15 Aug 2007 22:54:31 +0200 [thread overview]
Message-ID: <20070815205708.589061139@breakpoint.cc> (raw)
In-Reply-To: 20070815205430.512612422@breakpoint.cc
[-- Attachment #1: atomic_i386.diff --]
[-- Type: text/plain, Size: 1648 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=pentium-m and gcc (GCC) 4.1.2 (Gentoo 4.1.2):
text data bss dec hex filename
3434150 249176 176128 3859454 3ae3fe atomic_normal/vmlinux
3435308 249176 176128 3860612 3ae884 atomic_inlineasm/vmlinux
3436201 249176 176128 3861505 3aec01 atomic_inline_volatile/vmlinux
3436203 249176 176128 3861507 3aec03 atomic_volatile/vmlinux
Signed-off-by: Sebastian Siewior <sebastian@breakpoint.cc>
Cc: Andi Kleen <ak@suse.de>
Cc: Chris Snook <csnook@redhat.com>
--- a/include/asm-i386/atomic.h
+++ b/include/asm-i386/atomic.h
@@ -25,7 +25,16 @@ typedef struct { int counter; } 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
@@ -34,7 +43,13 @@ typedef struct { int counter; } atomic_t
*
* 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
--
next prev parent reply other threads:[~2007-08-15 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 20:54 [patch 0/2] use asm() for atomic_{read|set} (shot 2) Sebastian Siewior
2007-08-15 20:54 ` Sebastian Siewior [this message]
2007-08-15 20:54 ` [patch 2/2] x86_64: use asm() like the other atomic operations already do Sebastian Siewior
-- strict thread matches above, loose matches on Subject: below --
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
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=20070815205708.589061139@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=ak@suse.de \
--cc=csnook@redhat.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