From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932791AbaAaTrk (ORCPT ); Fri, 31 Jan 2014 14:47:40 -0500 Received: from merlin.infradead.org ([205.233.59.134]:54283 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752785AbaAaTri (ORCPT ); Fri, 31 Jan 2014 14:47:38 -0500 Date: Fri, 31 Jan 2014 20:47:18 +0100 From: Peter Zijlstra To: Waiman Long Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Arnd Bergmann , linux-arch@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, Steven Rostedt , Andrew Morton , Michel Lespinasse , Andi Kleen , Rik van Riel , "Paul E. McKenney" , Linus Torvalds , Raghavendra K T , George Spelvin , Tim Chen , aswin@hp.com, Scott J Norton Subject: Re: [PATCH v11 0/4] Introducing a queue read/write lock implementation Message-ID: <20140131194718.GO5002@laptop.programming.kicks-ass.net> References: <1390537731-45996-1-git-send-email-Waiman.Long@hp.com> <20140130130453.GB2936@laptop.programming.kicks-ass.net> <20140130151715.GA5126@laptop.programming.kicks-ass.net> <20140131092616.GC5126@laptop.programming.kicks-ass.net> <52EBF276.1020505@hp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52EBF276.1020505@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 On Fri, Jan 31, 2014 at 01:59:02PM -0500, Waiman Long wrote: > On 01/31/2014 04:26 AM, Peter Zijlstra wrote: > >On Thu, Jan 30, 2014 at 04:17:15PM +0100, Peter Zijlstra wrote: > >>The below is still small and actually works. > >OK, so having actually worked through the thing; I realized we can > >actually do a version without MCS lock and instead use a ticket lock for > >the waitqueue. > > > >This is both smaller (back to 8 bytes for the rwlock_t), and should be > >faster under moderate contention for not having to touch extra > >cachelines. > > > >Completely untested and with a rather crude generic ticket lock > >implementation to illustrate the concept: > > > > Using a ticket lock instead will have the same scalability problem as the > ticket spinlock as all the waiting threads will spin on the lock cacheline > causing a lot of cache bouncing traffic. That is the reason why I want to > replace ticket spinlock with queue spinlock. But but but, just fix such heavily contended locks. Don't make sensible code that is lightly contended run slower because of it.