From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [RFC PATCH 0/3] restartable sequences v2: fast user-space percpu critical sections Date: Fri, 8 Apr 2016 13:02:32 +0200 Message-ID: <20160408110232.GP3448@twins.programming.kicks-ass.net> References: <20151027235635.16059.11630.stgit@pjt-glaptop.roam.corp.google.com> <20160407120254.GY3448@twins.programming.kicks-ass.net> <20160407152432.GZ3448@twins.programming.kicks-ass.net> <20160407155312.GA3448@twins.programming.kicks-ass.net> <20160407201156.GC3448@twins.programming.kicks-ass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andy Lutomirski Cc: Mathieu Desnoyers , "Paul E. McKenney" , Ingo Molnar , Paul Turner , Andi Kleen , Chris Lameter , Dave Watson , Josh Triplett , Linux API , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Andrew Hunter , Linus Torvalds List-Id: linux-api@vger.kernel.org On Thu, Apr 07, 2016 at 03:05:26PM -0700, Andy Lutomirski wrote: > It doesn't, which is what I like about my variant. If the thread > accesses the protected data structure, though, it should bump the > sequence count, which will cause the first thread to about when it > gets scheduled in. Nope it won't, because that first thread is right at the commit instruction, nothing will stop it from executing that store and clobbing what we just wrote. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758175AbcDHLEL (ORCPT ); Fri, 8 Apr 2016 07:04:11 -0400 Received: from casper.infradead.org ([85.118.1.10]:32855 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754035AbcDHLEJ (ORCPT ); Fri, 8 Apr 2016 07:04:09 -0400 Date: Fri, 8 Apr 2016 13:02:32 +0200 From: Peter Zijlstra To: Andy Lutomirski Cc: Mathieu Desnoyers , "Paul E. McKenney" , Ingo Molnar , Paul Turner , Andi Kleen , Chris Lameter , Dave Watson , Josh Triplett , Linux API , "linux-kernel@vger.kernel.org" , Andrew Hunter , Linus Torvalds Subject: Re: [RFC PATCH 0/3] restartable sequences v2: fast user-space percpu critical sections Message-ID: <20160408110232.GP3448@twins.programming.kicks-ass.net> References: <20151027235635.16059.11630.stgit@pjt-glaptop.roam.corp.google.com> <20160407120254.GY3448@twins.programming.kicks-ass.net> <20160407152432.GZ3448@twins.programming.kicks-ass.net> <20160407155312.GA3448@twins.programming.kicks-ass.net> <20160407201156.GC3448@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 On Thu, Apr 07, 2016 at 03:05:26PM -0700, Andy Lutomirski wrote: > It doesn't, which is what I like about my variant. If the thread > accesses the protected data structure, though, it should bump the > sequence count, which will cause the first thread to about when it > gets scheduled in. Nope it won't, because that first thread is right at the commit instruction, nothing will stop it from executing that store and clobbing what we just wrote.