From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754602AbdEEPcv (ORCPT ); Fri, 5 May 2017 11:32:51 -0400 Received: from foss.arm.com ([217.140.101.70]:53048 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751769AbdEEPcs (ORCPT ); Fri, 5 May 2017 11:32:48 -0400 Date: Fri, 5 May 2017 16:32:46 +0100 From: Will Deacon To: Yury Norov Cc: Peter Zijlstra , pan xinhui , "linux-kernel@vger.kernel.org" , "linux-arch@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Adam Wallis , Andrew Pinski , Arnd Bergmann , Catalin Marinas , Ingo Molnar , Jan Glauber , Mark Rutland , Pan Xinhui Subject: Re: =?utf-8?B?562U5aSN?= =?utf-8?Q?=3A?= [PATCH 0/3] arm64: queued spinlocks and rw-locks Message-ID: <20170505153245.GH14111@arm.com> References: <20170503145141.4966-1-ynorov@caviumnetworks.com> <20170504202809.lv222a3oes54ijkj@yury-N73SV> <20170505115303.s3bsu4adfgkxrhh2@hirez.programming.kicks-ass.net> <20170505122639.GB14111@arm.com> <20170505152845.e32h3jxhjdjw6yht@yury-N73SV> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170505152845.e32h3jxhjdjw6yht@yury-N73SV> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 05, 2017 at 06:28:45PM +0300, Yury Norov wrote: > On Fri, May 05, 2017 at 01:26:40PM +0100, Will Deacon wrote: > > On Fri, May 05, 2017 at 01:53:03PM +0200, Peter Zijlstra wrote: > > > On Thu, May 04, 2017 at 11:28:09PM +0300, Yury Norov wrote: > > > > I don't think > > > > it's a real use case to have ticket spinlocks and queued rwlocks > > > > > > There's nothing wrong with that combination. In fact, we merged qrwlock > > > much earlier than qspinlock. > > > > ... and that's almost certainly the direction we'll go on arm64 too, not > > least because the former are a lot easier to grok. > > > > Will > > Hmm. Then I think I have to split patch 3 to rwlock and spinlock > parts, and allow user to enable them independently in config. To be honest, I'm going to spend some time looking at the qrwlock code again before I enable it for arm64, so I don't think you need to rush to resend patches since I suspect I'll have a few in the meantime. Will