Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752374Ab3I1Hyn (ORCPT ); Sat, 28 Sep 2013 03:54:43 -0400 Received: from merlin.infradead.org ([205.233.59.134]:39697 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751814Ab3I1Hyl (ORCPT ); Sat, 28 Sep 2013 03:54:41 -0400 Date: Sat, 28 Sep 2013 09:54:09 +0200 From: Peter Zijlstra To: Oliver Neukum Cc: Joe Perches , Ingo Molnar , Tim Chen , Jason Low , Davidlohr Bueso , Ingo Molnar , Andrew Morton , Andrea Arcangeli , Alex Shi , Andi Kleen , Michel Lespinasse , Davidlohr Bueso , Matthew R Wilcox , Dave Hansen , Rik van Riel , Peter Hurley , linux-kernel@vger.kernel.org, linux-mm Subject: Re: [PATCH] checkpatch: Make the memory barrier test noisier Message-ID: <20130928075409.GK15690@laptop.programming.kicks-ass.net> References: <1380236265.3467.103.camel@schen9-DESK> <20130927060213.GA6673@gmail.com> <20130927112323.GJ3657@laptop.programming.kicks-ass.net> <1380289495.17366.91.camel@joe-AO722> <20130927134802.GA15690@laptop.programming.kicks-ass.net> <1380291257.17366.103.camel@joe-AO722> <20130927142605.GC15690@laptop.programming.kicks-ass.net> <1380292495.17366.106.camel@joe-AO722> <20130927145007.GD15690@laptop.programming.kicks-ass.net> <1380325227.1631.2.camel@linux-fkkt.site> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1380325227.1631.2.camel@linux-fkkt.site> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 972 Lines: 22 On Sat, Sep 28, 2013 at 01:40:27AM +0200, Oliver Neukum wrote: > On Fri, 2013-09-27 at 16:50 +0200, Peter Zijlstra wrote: > > On Fri, Sep 27, 2013 at 07:34:55AM -0700, Joe Perches wrote: > > > That would make it seem as if all barriers are SMP no? > > > > I would think any memory barrier is ordering against someone else; if > > not smp then a device/hardware -- like for instance the hardware page > > table walker. > > > > Barriers are fundamentally about order; and order only makes sense if > > there's more than 1 party to the game. > > But not necessarily more than 1 kind of parties. It is perfectly > possible to have a barrier against other threads running the same > function. Then that makes a good comment ;-) -- 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/