From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753792AbbGNLbw (ORCPT ); Tue, 14 Jul 2015 07:31:52 -0400 Received: from foss.arm.com ([217.140.101.70]:33875 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751830AbbGNLbu (ORCPT ); Tue, 14 Jul 2015 07:31:50 -0400 Date: Tue, 14 Jul 2015 12:31:47 +0100 From: Will Deacon To: Peter Zijlstra Cc: "linux-arch@vger.kernel.org" , "Waiman.Long@hp.com" , "linux-kernel@vger.kernel.org" , "paulmck@linux.vnet.ibm.com" Subject: Re: [PATCH 1/5] atomics: add acquire/release/relaxed variants of some atomic operations Message-ID: <20150714113147.GF16213@arm.com> References: <1436790687-11984-1-git-send-email-will.deacon@arm.com> <1436790687-11984-2-git-send-email-will.deacon@arm.com> <20150714102511.GI19282@twins.programming.kicks-ass.net> <20150714103220.GB16213@arm.com> <20150714105837.GJ19282@twins.programming.kicks-ass.net> <20150714110811.GE16213@arm.com> <20150714112420.GK3644@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150714112420.GK3644@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 14, 2015 at 12:24:20PM +0100, Peter Zijlstra wrote: > On Tue, Jul 14, 2015 at 12:08:11PM +0100, Will Deacon wrote: > > On Tue, Jul 14, 2015 at 11:58:37AM +0100, Peter Zijlstra wrote: > > > > > #ifndef atomic_add_return_relaxed > > > > > > #define atomic_add_return_relaxed atomic_add_return > > > /* > > > * If one cannot define a more relaxed version, > > > * acquire/release are out the window too. > > > */ > > > #define atomic_add_return_acquire atomic_add_return > > > #define atomic_add_return_release atomic_add_return > > > > > > #else /* relaxed */ > > > > > > #ifndef atomic_add_return_acquire > > > #define atomic_add_return_acquire(args...) \ > > > do { \ > > > atomic_add_return_relaxed(args); \ > > > smp_mb__after_atomic(); \ > > > } while (0) > > > #endif > > > > > > #ifndef atomic_add_return_release > > > #define atomic_add_return_release(args...) \ > > > do { \ > > > smp_mb__before_atomic(); \ > > > atomic_add_return_relaxed(args); \ > > > } while (0) > > > #endif > > One could even take it one step further and go: > > #ifndef atomic_add_return > #define atomic_add_return(args...) \ > do { \ > smp_mb__before_atomic(); \ > atomid_add_return_relaxed(args); \ > smp_mb__after_atomic(); \ > } while (0) ...and #ifndef atomic_add #define atomic_add(args...) (void)atomic_add_return_relaxed(args); It would mean a new architecture only has to define a barrier instruction and a handful of relaxed atomics for a bare-minimum atomic.h avoiding spinlocks. Will