Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758154Ab1FFWeI (ORCPT ); Mon, 6 Jun 2011 18:34:08 -0400 Received: from mail-fx0-f46.google.com ([209.85.161.46]:32913 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756634Ab1FFWeG convert rfc822-to-8bit (ORCPT ); Mon, 6 Jun 2011 18:34:06 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=rb+o10EdoxM/KFtUW2tuseo3XtwCiUoVaD7aFW74xskxBg/0NtK53aD5tm/Rgt9ZRR +YakLAPJPmxB+b3VDjNw1yp9iefqoRMaNCSodP4hglatk3uaKXwi63wmbitPSEDiWYr7 54O254Hx3gcw6IKH3PZ7aL13DED5u2GM/H2KI= MIME-Version: 1.0 In-Reply-To: References: <1306725568-10922-1-git-send-email-vapier@gentoo.org> <20110606142301.c0a570da.akpm@linux-foundation.org> From: Mike Frysinger Date: Mon, 6 Jun 2011 18:33:44 -0400 X-Google-Sender-Auth: n_AJ3YuqDXEAwW3jri4AG5me9J0 Message-ID: Subject: Re: [uclinux-dist-devel] [PATCH/RFC] asm-generic/mutex-dec.h: add SMP support To: Andrew Morton Cc: linux-arch@vger.kernel.org, Piggin , Arnd Bergmann , linux-kernel@vger.kernel.org, Nick@blackfin.uclinux.org, uclinux-dist-devel@blackfin.uclinux.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2744 Lines: 68 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/