From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 3CED92C00A2 for ; Tue, 11 Feb 2014 21:40:38 +1100 (EST) Date: Tue, 11 Feb 2014 11:40:30 +0100 From: Torsten Duwe To: Raghavendra KT Subject: Re: [PATCH v2] powerpc ticket locks Message-ID: <20140211104030.GG2107@lst.de> References: <20140207165801.GC2107@lst.de> <1392001823.3996.21.camel@pasglop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: Tom Musta , Peter Zijlstra , Raghavendra KT , Linux Kernel Mailing List , Paul Mackerras , Anton Blanchard , Scott Wood , "Paul E. McKenney" , linuxppc-dev@lists.ozlabs.org, Ingo Molnar List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Feb 11, 2014 at 03:23:51PM +0530, Raghavendra KT wrote: > How much important to have holder information for PPC? From my > previous experiment > on x86, it was lock-waiter preemption which is problematic rather than > lock-holder preemption. It's something very special to IBM pSeries: the hypervisor can assign fractions of physical CPUs to guests. Sometimes a guest with 4 quarter CPUs will be faster than 1 monoprocessor. (correct me if I'm wrong). The directed yield resolves the silly situation when holder and waiter reside on the same physical CPU, as I understand it. x86 has nothing comparable. Torsten