From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935444AbcA0Sjc (ORCPT ); Wed, 27 Jan 2016 13:39:32 -0500 Received: from foss.arm.com ([217.140.101.70]:54788 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935036AbcA0Sj0 (ORCPT ); Wed, 27 Jan 2016 13:39:26 -0500 Date: Wed, 27 Jan 2016 18:39:23 +0000 From: Will Deacon To: Peter Zijlstra Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Boqun Feng , "Paul E. McKenney" Subject: Re: [PATCH v3] barriers: introduce smp_mb__release_acquire and update documentation Message-ID: <20160127183923.GD25545@arm.com> References: <1453918924-27606-1-git-send-email-will.deacon@arm.com> <20160127182551.GX6357@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160127182551.GX6357@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 Wed, Jan 27, 2016 at 07:25:51PM +0100, Peter Zijlstra wrote: > On Wed, Jan 27, 2016 at 06:22:04PM +0000, Will Deacon wrote: > > As much as we'd like to live in a world where RELEASE -> ACQUIRE is > > always cheaply ordered and can be used to construct UNLOCK -> LOCK > > definitions with similar guarantees, the grim reality is that this isn't > > even possible on x86 (thanks to Paul for bringing us crashing down to > > Earth). > > > > This patch handles the issue by introducing a new barrier macro, > > smp_mb__after_release_acquire, that can be placed after an ACQUIRE that > > either reads from a RELEASE or is in program-order after a RELEASE. The > > barrier upgrades the RELEASE-ACQUIRE pair to a full memory barrier, > > implying global transitivity. At the moment, it doesn't have any users, > > so its existence serves mainly as a documentation aid and a potential > > stepping stone to the reintroduction of smp_mb__after_unlock_lock() used > > by RCU. > > > > Documentation/memory-barriers.txt is updated to describe more clearly > > the ACQUIRE and RELEASE ordering in this area and to show some examples > > of the new barrier in action. > > So the obvious question is: do we have a use-case? We have a use-case for smp_mb__after_unlock_lock, so I think we should either strengthen our locking guarantees so that smp_mb__after_unlock_lock isn't needed or introduce smp_mb__after_release_acquire to close the gap. As it stands, we've got an inconsistency (despite it being hidden inside RCU). The main advantage of this patch is a documentation aid, in my opinion (hell, we talk about smp_mb__after_unlock_lock already when reasoning about this stuff). Will