From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Nicolas Pitre <nico@cam.org>,
Joel Schopp <jschopp@austin.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjan@infradead.org>,
Jes Sorensen <jes@trained-monkey.org>,
Al Viro <viro@ftp.linux.org.uk>, Oleg Nesterov <oleg@tv-sign.ru>,
David Howells <dhowells@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Anton Blanchard <anton@samba.org>
Subject: Re: [patch 00/21] mutex subsystem, -V14
Date: Thu, 5 Jan 2006 15:40:16 +0100 [thread overview]
Message-ID: <20060105144016.GB16816@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0601041847330.3279@g5.osdl.org>
* Linus Torvalds <torvalds@osdl.org> wrote:
> Well, if the generic one generates _buggy_ code on ppc64, that means
> that either the generic version is buggy, or one of the atomics that
> it uses is buggily implemented on ppc64.
>
> And I think it's the generic mutex stuff that is buggy. It seems to
> assume memory barriers that aren't valid to assume.
in those headers i'm only using atomic_dec_return(), atomic_cmpxchg()
and atomic_xchg() - all of which imply a barrier. It is
atomic_inc/add/sub/dec() that doesnt default to an implied SMP barrier.
but it's certainly not documented too well. If atomic_dec_return() is
not supposed to imply a barrier, then all the affected architectures
(sparc64, ppc64, mips, alpha, etc.) are overdoing synchronization
currently: they all have barriers for these primitives. [They also have
an implicit barrier for atomic_dec_test() - which is being relied on for
correctness - no kernel code adds an smp_mb__before_atomic_dec() barrier
to around atomic_dec_test().]
the patch below adds the barriers to the asm-generic mutex routines, so
it's not like i'm lazy ;), but i really think this is unnecessary.
Adding this patch would add a second, unnecessary barrier for all the
arches that have barrier-less atomic ops.
it also makes sense: the moment you are interested in the 'previous
value' of the atomic counter in an atomic fashion, you very likely want
to use it for a critical section. (e.g. all the put-the-resource ops
that use atomic_dec_test() rely on this implicit barrier.)
Ingo
Index: linux/include/asm-generic/mutex-dec.h
===================================================================
--- linux.orig/include/asm-generic/mutex-dec.h
+++ linux/include/asm-generic/mutex-dec.h
@@ -19,6 +19,7 @@
*/
#define __mutex_fastpath_lock(count, fail_fn) \
do { \
+ smp_mb__before_atomic_dec(); \
if (unlikely(atomic_dec_return(count) < 0)) \
fail_fn(count); \
} while (0)
@@ -36,6 +37,7 @@ do { \
static inline int
__mutex_fastpath_lock_retval(atomic_t *count, int (*fail_fn)(atomic_t *))
{
+ smp_mb__before_atomic_dec();
if (unlikely(atomic_dec_return(count) < 0))
return fail_fn(count);
else
@@ -59,6 +61,8 @@ __mutex_fastpath_lock_retval(atomic_t *c
do { \
if (unlikely(atomic_inc_return(count) <= 0)) \
fail_fn(count); \
+ else \
+ smp_mb__after_atomic_inc(); \
} while (0)
#define __mutex_slowpath_needs_to_unlock() 1
@@ -92,6 +96,7 @@ __mutex_fastpath_trylock(atomic_t *count
* the mutex state would be.
*/
#ifdef __HAVE_ARCH_CMPXCHG
+ smp_mb__before_atomic_dec();
if (likely(atomic_cmpxchg(count, 1, 0)) == 1)
return 1;
return 0;
Index: linux/include/asm-generic/mutex-xchg.h
===================================================================
--- linux.orig/include/asm-generic/mutex-xchg.h
+++ linux/include/asm-generic/mutex-xchg.h
@@ -24,6 +24,7 @@
*/
#define __mutex_fastpath_lock(count, fail_fn) \
do { \
+ smp_mb__before_atomic_dec(); \
if (unlikely(atomic_xchg(count, 0) != 1)) \
fail_fn(count); \
} while (0)
@@ -42,6 +43,7 @@ do { \
static inline int
__mutex_fastpath_lock_retval(atomic_t *count, int (*fail_fn)(atomic_t *))
{
+ smp_mb__before_atomic_dec();
if (unlikely(atomic_xchg(count, 0) != 1))
return fail_fn(count);
else
@@ -64,6 +66,8 @@ __mutex_fastpath_lock_retval(atomic_t *c
do { \
if (unlikely(atomic_xchg(count, 1) != 0)) \
fail_fn(count); \
+ else \
+ smp_mb__after_atomic_inc(); \
} while (0)
#define __mutex_slowpath_needs_to_unlock() 0
@@ -86,7 +90,10 @@ do { \
static inline int
__mutex_fastpath_trylock(atomic_t *count, int (*fail_fn)(atomic_t *))
{
- int prev = atomic_xchg(count, 0);
+ int prev;
+
+ smp_mb__before_atomic_dec();
+ prev = atomic_xchg(count, 0);
if (unlikely(prev < 0)) {
/*
next prev parent reply other threads:[~2006-01-05 14:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 14:41 Ingo Molnar
2006-01-04 23:45 ` Joel Schopp
2006-01-05 2:38 ` Nicolas Pitre
2006-01-05 2:51 ` Linus Torvalds
2006-01-05 3:21 ` Nick Piggin
2006-01-05 3:39 ` Anton Blanchard
2006-01-05 18:04 ` Jesse Barnes
2006-01-05 14:40 ` Ingo Molnar [this message]
2006-01-05 16:21 ` Linus Torvalds
2006-01-05 22:03 ` Ingo Molnar
2006-01-05 22:17 ` Linus Torvalds
2006-01-05 22:43 ` Ingo Molnar
2006-01-06 3:49 ` Keith Owens
2006-01-06 7:34 ` Denis Vlasenko
2006-01-05 14:35 ` Ingo Molnar
2006-01-05 16:42 ` Joel Schopp
2006-01-05 22:21 ` Ingo Molnar
2006-01-05 23:06 ` Joel Schopp
2006-01-05 23:26 ` Linus Torvalds
2006-01-05 23:36 ` Joel Schopp
2006-01-05 23:42 ` Ingo Molnar
2006-01-06 0:29 ` Olof Johansson
2006-01-07 17:49 ` PowerPC fastpaths for mutex subsystem Joel Schopp
2006-01-07 22:37 ` Andrew Morton
2006-01-08 7:43 ` Anton Blanchard
2006-01-08 8:00 ` Andrew Morton
2006-01-08 8:23 ` Anton Blanchard
2006-01-09 11:13 ` David Howells
2006-01-08 9:48 ` Ingo Molnar
2006-01-10 22:31 ` Joel Schopp
2006-01-10 23:09 ` Ingo Molnar
2006-01-11 10:52 ` Ingo Molnar
2006-01-11 17:44 ` Joel Schopp
2006-01-08 10:43 ` Ingo Molnar
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=20060105144016.GB16816@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton@samba.org \
--cc=arjan@infradead.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jes@trained-monkey.org \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.org \
--cc=oleg@tv-sign.ru \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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®