From: Mike Frysinger <vapier@gentoo.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arch@vger.kernel.org, Piggin <npiggin@kernel.dk>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, Nick@blackfin.uclinux.org,
uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [uclinux-dist-devel] [PATCH/RFC] asm-generic/mutex-dec.h: add SMP support
Date: Mon, 6 Jun 2011 18:33:44 -0400 [thread overview]
Message-ID: <BANLkTimRpcygQT-M1PJNOQCeeR46j8Vw+g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikq5-a8a5A4iq=3Br-m+PhuKYSePA@mail.gmail.com>
On Mon, Jun 6, 2011 at 17:31, Mike Frysinger wrote:
> On Mon, Jun 6, 2011 at 17:23, Andrew Morton wrote:
>> On Sun, 29 May 2011 23:19:28 -0400 Mike Frysinger wrote:
>>> To make these guys work on SMP systems, we just need to sprinkle a few
>>> barriers around.
>>>
>>> diff --git a/include/asm-generic/mutex-dec.h b/include/asm-generic/mutex-dec.h
>>> index f104af7..e746c3c 100644
>>> --- a/include/asm-generic/mutex-dec.h
>>> +++ b/include/asm-generic/mutex-dec.h
>>> @@ -22,6 +22,8 @@ __mutex_fastpath_lock(atomic_t *count, void (*fail_fn)(atomic_t *))
>>> {
>>> if (unlikely(atomic_dec_return(count) < 0))
>>> fail_fn(count);
>>> + else
>>> + smp_mb();
>>> }
>>>
>>> /**
>>> @@ -39,6 +41,7 @@ __mutex_fastpath_lock_retval(atomic_t *count, int (*fail_fn)(atomic_t *))
>>> {
>>> if (unlikely(atomic_dec_return(count) < 0))
>>> return fail_fn(count);
>>> + smp_mb();
>>> return 0;
>>> }
>>>
>>> @@ -58,6 +61,7 @@ __mutex_fastpath_lock_retval(atomic_t *count, int (*fail_fn)(atomic_t *))
>>> static inline void
>>> __mutex_fastpath_unlock(atomic_t *count, void (*fail_fn)(atomic_t *))
>>> {
>>> + smp_mb();
>>> if (unlikely(atomic_inc_return(count) <= 0))
>>> fail_fn(count);
>>> }
>>> @@ -82,8 +86,10 @@ __mutex_fastpath_unlock(atomic_t *count, void (*fail_fn)(atomic_t *))
>>> static inline int
>>> __mutex_fastpath_trylock(atomic_t *count, int (*fail_fn)(atomic_t *))
>>> {
>>> - if (likely(atomic_cmpxchg(count, 1, 0) == 1))
>>> + if (likely(atomic_cmpxchg(count, 1, 0) == 1)) {
>>> + smp_mb();
>>> return 1;
>>> + }
>>> return 0;
>>> }
>>
>> This patch basically reverts Nick's a8ddac7e53e89cb ("mutex: speed up
>> generic mutex implementations"). What's up with that?
>>
>> I could try to review this patch but I'm pathetic with barriers. Help.
>
> thanks for that tip. i think we can chalk this patch up to the
> origins of the Blackfin SMP port ... it branched this code before
> Nick's patch, and never incorporated common changes back. so i'll
> just drop it once i boot up a system to double check and convert the
> Blackfin code over to the asm-generic version completely to avoid
> future issues.
seems to be ok (and our core atomic's do include barriers themselves),
so let's just drop this patch on the floor and forget about it.
thanks all!
-mike
next prev parent reply other threads:[~2011-06-06 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 3:19 [PATCH/RFC] asm-generic/mutex-dec.h: add SMP support Mike Frysinger
2011-05-30 7:00 ` Arnd Bergmann
2011-06-06 21:23 ` Andrew Morton
2011-06-06 21:31 ` [uclinux-dist-devel] " Mike Frysinger
2011-06-06 22:33 ` Mike Frysinger [this message]
2011-06-06 21:32 ` Eric Dumazet
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=BANLkTimRpcygQT-M1PJNOQCeeR46j8Vw+g@mail.gmail.com \
--to=vapier@gentoo.org \
--cc=Nick@blackfin.uclinux.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=uclinux-dist-devel@blackfin.uclinux.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;
as well as URLs for NNTP newsgroup(s).