From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) by kanga.kvack.org (Postfix) with ESMTP id 46F4B6B0035 for ; Sat, 23 Nov 2013 15:39:55 -0500 (EST) Received: by mail-vc0-f177.google.com with SMTP id hv10so1744110vcb.22 for ; Sat, 23 Nov 2013 12:39:55 -0800 (PST) Received: from mail-vc0-x22c.google.com (mail-vc0-x22c.google.com [2607:f8b0:400c:c03::22c]) by mx.google.com with ESMTPS id sl9si94682vdc.138.2013.11.23.12.39.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 23 Nov 2013 12:39:54 -0800 (PST) Received: by mail-vc0-f172.google.com with SMTP id hz11so1771820vcb.3 for ; Sat, 23 Nov 2013 12:39:54 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20131122184937.GX4138@linux.vnet.ibm.com> <20131122200620.GA4138@linux.vnet.ibm.com> <20131122203738.GC4138@linux.vnet.ibm.com> <20131122215208.GD4138@linux.vnet.ibm.com> <20131123002542.GF4138@linux.vnet.ibm.com> <20131123013654.GG4138@linux.vnet.ibm.com> Date: Sat, 23 Nov 2013 12:39:53 -0800 Message-ID: Subject: Re: [PATCH v6 4/5] MCS Lock: Barrier corrections From: Linus Torvalds Content-Type: text/plain; charset=UTF-8 Sender: owner-linux-mm@kvack.org List-ID: To: Paul McKenney Cc: Ingo Molnar , Tim Chen , Will Deacon , Ingo Molnar , Andrew Morton , Thomas Gleixner , "linux-kernel@vger.kernel.org" , linux-mm , "linux-arch@vger.kernel.org" , Waiman Long , Andrea Arcangeli , Alex Shi , Andi Kleen , Michel Lespinasse , Davidlohr Bueso , Matthew R Wilcox , Dave Hansen , Peter Zijlstra , Rik van Riel , Peter Hurley , Raghavendra K T , George Spelvin , "H. Peter Anvin" , Arnd Bergmann , Aswin Chandramouleeswaran , Scott J Norton , "Figo.zhang" On Sat, Nov 23, 2013 at 12:21 PM, Linus Torvalds wrote: > > And as far as I can tell, the above gives you: A < B < C < D < E < F < > A. Which doesn't look possible. Hmm.. I guess technically all of those cases aren't "strictly precedes" as much as "cannot have happened in the opposite order". So the "<" might be "<=". Which I guess *is* possible: "it all happened at the same time". And then the difference between your suggested "lwsync" and "sync" in the unlock path on CPU0 basically approximating the difference between "A <= B" and "A < B".. Ho humm. Linus -- 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