From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933207Ab0KLWOJ (ORCPT ); Fri, 12 Nov 2010 17:14:09 -0500 Received: from terminus.zytor.com ([198.137.202.10]:52086 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933186Ab0KLWOF (ORCPT ); Fri, 12 Nov 2010 17:14:05 -0500 Message-ID: <4CDDBBD3.5050903@zytor.com> Date: Fri, 12 Nov 2010 14:12:35 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101027 Fedora/3.1.6-1.fc13 Thunderbird/3.1.6 MIME-Version: 1.0 To: Jeremy Fitzhardinge CC: Peter Zijlstra , Linux Kernel Mailing List , Nick Piggin , Jan Beulich , Avi Kivity , Xen-devel , Linux Virtualization , Srivatsa Vaddagiri , Jeremy Fitzhardinge Subject: Re: [PATCH 00/20] x86: ticket lock rewrite and paravirtualization References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/03/2010 07:59 AM, Jeremy Fitzhardinge wrote: > > - with an unmodified struct spinlock, it can check to see if > head == tail after unlock; if not, then there's someone else > trying to lock, and we can do a kick. Unfortunately this > generates very high level of redundant kicks, because the > waiting CPU might not have blocked yet (which is the common > case) > How high is "very high" here -- most of the time (so that any mitigation on the slow patch is useless)? -hpa