From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933883AbbJIRp1 (ORCPT ); Fri, 9 Oct 2015 13:45:27 -0400 Received: from e39.co.us.ibm.com ([32.97.110.160]:40418 "EHLO e39.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933844AbbJIRpV (ORCPT ); Fri, 9 Oct 2015 13:45:21 -0400 X-IBM-Helo: d03dlp03.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com X-IBM-RcptTo: linux-arch@vger.kernel.org;linux-kernel@vger.kernel.org Date: Fri, 9 Oct 2015 10:44:18 -0700 From: "Paul E. McKenney" To: Peter Zijlstra Cc: Will Deacon , Michael Ellerman , linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Boqun Feng , Anton Blanchard , Benjamin Herrenschmidt , Paul Mackerras , linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH v2] barriers: introduce smp_mb__release_acquire and update documentation Message-ID: <20151009174418.GW3910@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <1444215568-24732-1-git-send-email-will.deacon@arm.com> <20151007111915.GF17308@twins.programming.kicks-ass.net> <20151007132317.GK16065@arm.com> <20151007152501.GI3910@linux.vnet.ibm.com> <1444276236.9940.5.camel@ellerman.id.au> <20151008111638.GL3816@twins.programming.kicks-ass.net> <20151008125937.GH16807@arm.com> <20151008221716.GF3910@linux.vnet.ibm.com> <20151009095129.GF26278@arm.com> <20151009112554.GB3816@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151009112554.GB3816@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15100917-0033-0000-0000-0000064E9E23 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 09, 2015 at 01:25:54PM +0200, Peter Zijlstra wrote: > On Fri, Oct 09, 2015 at 10:51:29AM +0100, Will Deacon wrote: > > > The corresponding litmus tests are below. > > > > How do people feel about including these in memory-barriers.txt? I find > > them considerably easier to read than our current kernel code + list of > > possible orderings + wall of text, but there's a good chance that my > > brain has been corrupted from staring at this stuff for too long. > > Your brain is corrupt (but then, so probably is mine, just differently > so). > > I've not yet mastered the knack of reading those things; then again, I > suspect its not too hard, just not something I've had the time to play > with. It does take a bit of practice, but is worth the effort. Of course, I -would- say that. ;-) Thanx, Paul