From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752412AbbINTif (ORCPT ); Mon, 14 Sep 2015 15:38:35 -0400 Received: from g2t4618.austin.hp.com ([15.73.212.83]:39278 "EHLO g2t4618.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752181AbbINTie (ORCPT ); Mon, 14 Sep 2015 15:38:34 -0400 Message-ID: <55F72238.1040903@hpe.com> Date: Mon, 14 Sep 2015 15:38:32 -0400 From: Waiman Long User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: Peter Zijlstra 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 v6 5/6] locking/pvqspinlock: Allow 1 lock stealing attempt References: <1441996658-62854-1-git-send-email-Waiman.Long@hpe.com> <1441996658-62854-6-git-send-email-Waiman.Long@hpe.com> <20150914140051.GT18489@twins.programming.kicks-ass.net> <55F71CC8.3050306@hpe.com> In-Reply-To: <55F71CC8.3050306@hpe.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/14/2015 03:15 PM, Waiman Long wrote: > On 09/14/2015 10:00 AM, Peter Zijlstra wrote: >> On Fri, Sep 11, 2015 at 02:37:37PM -0400, Waiman Long wrote: >>> This patch allows one attempt for the lock waiter to steal the lock >>> when entering the PV slowpath. This helps to reduce the performance >>> penalty caused by lock waiter preemption while not having much of >>> the downsides of a real unfair lock. >>> @@ -415,8 +458,12 @@ static void pv_wait_head(struct qspinlock >>> *lock, struct mcs_spinlock *node) >>> >>> for (;; waitcnt++) { >>> for (loop = SPIN_THRESHOLD; loop; loop--) { >>> - if (!READ_ONCE(l->locked)) >>> - return; >>> + /* >>> + * Try to acquire the lock when it is free. >>> + */ >>> + if (!READ_ONCE(l->locked)&& >>> + (cmpxchg(&l->locked, 0, _Q_LOCKED_VAL) == 0)) >>> + goto gotlock; >>> cpu_relax(); >>> } >>> >> This isn't _once_, this is once per 'wakeup'. And note that interrupts >> unrelated to the kick can equally wake the vCPU up. >> > > Oh! There is a minor bug that I shouldn't need to have a second > READ_ONCE() call here. Oh! I misread the diff, the code was OK. Cheers, Longman