Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966344AbaFRLkt (ORCPT ); Wed, 18 Jun 2014 07:40:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45127 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966054AbaFRLkr (ORCPT ); Wed, 18 Jun 2014 07:40:47 -0400 Message-ID: <53A17A88.7090705@redhat.com> Date: Wed, 18 Jun 2014 13:39:52 +0200 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Peter Zijlstra , Waiman.Long@hp.com, tglx@linutronix.de, mingo@kernel.org CC: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, xen-devel@lists.xenproject.org, kvm@vger.kernel.org, paolo.bonzini@gmail.com, konrad.wilk@oracle.com, boris.ostrovsky@oracle.com, paulmck@linux.vnet.ibm.com, riel@redhat.com, torvalds@linux-foundation.org, raghavendra.kt@linux.vnet.ibm.com, david.vrabel@citrix.com, oleg@redhat.com, gleb@redhat.com, scott.norton@hp.com, chegu_vinod@hp.com, Peter Zijlstra Subject: Re: [PATCH 05/11] qspinlock: Optimize for smaller NR_CPUS References: <20140615124657.264658593@chello.nl> <20140615130153.483502389@chello.nl> In-Reply-To: <20140615130153.483502389@chello.nl> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 15/06/2014 14:47, Peter Zijlstra ha scritto: > > - for (;;) { > - new = (val & ~_Q_PENDING_MASK) | _Q_LOCKED_VAL; > - > - old = atomic_cmpxchg(&lock->val, val, new); > - if (old == val) > - break; > - > - val = old; > - } > + clear_pending_set_locked(lock, val); > return; Might as well add clear_pending_set_locked already in patch 3. Paolo -- 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/