Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752719AbbGPFtT (ORCPT ); Thu, 16 Jul 2015 01:49:19 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:40226 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752163AbbGPFtS (ORCPT ); Thu, 16 Jul 2015 01:49:18 -0400 Date: Thu, 16 Jul 2015 07:49:11 +0200 From: Peter Zijlstra To: Waiman Long Cc: Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, Scott J Norton , Douglas Hatch , Davidlohr Bueso Subject: Re: [PATCH v2 5/6] locking/pvqspinlock: Opportunistically defer kicking to unlock time Message-ID: <20150716054911.GW19282@twins.programming.kicks-ass.net> References: <1436926417-20256-1-git-send-email-Waiman.Long@hp.com> <1436926417-20256-6-git-send-email-Waiman.Long@hp.com> <20150715100309.GJ2859@worktop.programming.kicks-ass.net> <55A7147B.8020406@hp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55A7147B.8020406@hp.com> 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: 912 Lines: 20 On Wed, Jul 15, 2015 at 10:18:35PM -0400, Waiman Long wrote: > On 07/15/2015 06:03 AM, Peter Zijlstra wrote: > >*groan*, so you complained the previous version of this patch was too > >complex, but let me say I vastly preferred it to this one :/ > > I said it was complex as maintaining a tri-state variable needed more > thought than 2 bi-state variables. I can revert it back to the tri-state > variable as doing an unconditional kick in unlock simplifies the code at > pv_wait_head(). Well, your state space isn't shrunk, you just use more variables and I'm not entirely sure that actually matters. What also doesn't help is that mixing with the kicking code. -- 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/