From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by kanga.kvack.org (Postfix) with ESMTP id 528C16B0095 for ; Tue, 5 Nov 2013 16:18:44 -0500 (EST) Received: by mail-pa0-f44.google.com with SMTP id fb1so9542187pad.31 for ; Tue, 05 Nov 2013 13:18:43 -0800 (PST) Received: from psmtp.com ([74.125.245.198]) by mx.google.com with SMTP id gw3si15002988pac.346.2013.11.05.13.18.37 for ; Tue, 05 Nov 2013 13:18:38 -0800 (PST) Date: Tue, 5 Nov 2013 22:18:03 +0100 From: Peter Zijlstra Subject: Re: [PATCH v2 3/4] MCS Lock: Barrier corrections Message-ID: <20131105211803.GS28601@twins.programming.kicks-ass.net> References: <1383673356.11046.279.camel@schen9-DESK> <20131105183744.GJ26895@mudshark.cambridge.arm.com> <1383679317.11046.293.camel@schen9-DESK> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1383679317.11046.293.camel@schen9-DESK> Sender: owner-linux-mm@kvack.org List-ID: To: Tim Chen Cc: Will Deacon , Ingo Molnar , Andrew Morton , Thomas Gleixner , "linux-kernel@vger.kernel.org" , linux-mm , "linux-arch@vger.kernel.org" , Linus Torvalds , Waiman Long , Andrea Arcangeli , Alex Shi , Andi Kleen , Michel Lespinasse , Davidlohr Bueso , Matthew R Wilcox , Dave Hansen , Rik van Riel , Peter Hurley , "Paul E.McKenney" , Raghavendra K T , George Spelvin , "H. Peter Anvin" , Arnd Bergmann , Aswin Chandramouleeswaran , Scott J Norton On Tue, Nov 05, 2013 at 11:21:57AM -0800, Tim Chen wrote: > On Tue, 2013-11-05 at 18:37 +0000, Will Deacon wrote: > > On Tue, Nov 05, 2013 at 05:42:36PM +0000, Tim Chen wrote: > > > This patch corrects the way memory barriers are used in the MCS lock > > > and removes ones that are not needed. Also add comments on all barriers. > > > > Hmm, I see that you're fixing up the barriers, but I still don't completely > > understand how what you have is correct. Hopefully you can help me out :) > > > > > Reviewed-by: Paul E. McKenney > > > Reviewed-by: Tim Chen > > > Signed-off-by: Jason Low > > > --- > > > include/linux/mcs_spinlock.h | 13 +++++++++++-- > > > 1 files changed, 11 insertions(+), 2 deletions(-) > > > > > > diff --git a/include/linux/mcs_spinlock.h b/include/linux/mcs_spinlock.h > > > index 96f14299..93d445d 100644 > > > --- a/include/linux/mcs_spinlock.h > > > +++ b/include/linux/mcs_spinlock.h > > > @@ -36,16 +36,19 @@ void mcs_spin_lock(struct mcs_spinlock **lock, struct mcs_spinlock *node) > > > node->locked = 0; > > > node->next = NULL; > > > > > > + /* xchg() provides a memory barrier */ > > > prev = xchg(lock, node); > > > if (likely(prev == NULL)) { > > > /* Lock acquired */ > > > return; > > > } > > > ACCESS_ONCE(prev->next) = node; > > > - smp_wmb(); > > > /* Wait until the lock holder passes the lock down */ > > > while (!ACCESS_ONCE(node->locked)) > > > arch_mutex_cpu_relax(); > > > + > > > + /* Make sure subsequent operations happen after the lock is acquired */ > > > + smp_rmb(); > > > > Ok, so this is an smp_rmb() because we assume that stores aren't speculated, > > right? (i.e. the control dependency above is enough for stores to be ordered > > with respect to taking the lock)... PaulMck completely confused me a few days ago with control dependencies etc.. Pretty much saying that C/C++ doesn't do those. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org