From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936687Ab2C3XFD (ORCPT ); Fri, 30 Mar 2012 19:05:03 -0400 Received: from www.linutronix.de ([62.245.132.108]:41983 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934194Ab2C3XE5 (ORCPT ); Fri, 30 Mar 2012 19:04:57 -0400 Date: Sat, 31 Mar 2012 01:04:41 +0200 (CEST) From: Thomas Gleixner To: Andi Kleen cc: "H. Peter Anvin" , Raghavendra K T , Ingo Molnar , Linus Torvalds , Peter Zijlstra , the arch/x86 maintainers , LKML , Avi Kivity , Marcelo Tosatti , KVM , Xen Devel , Konrad Rzeszutek Wilk , Virtualization , Jeremy Fitzhardinge , Stephan Diestelhorst , Srivatsa Vaddagiri , Stefano Stabellini , Attilio Rao Subject: Re: [PATCH RFC V6 0/11] Paravirtualized ticketlocks In-Reply-To: <20120330221836.GN17822@one.firstfloor.org> Message-ID: References: <20120321102041.473.61069.sendpatchset@codeblue.in.ibm.com> <4F7616F5.4070000@zytor.com> <20120330221836.GN17822@one.firstfloor.org> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 31 Mar 2012, Andi Kleen wrote: > > So if a guest exits due to an external event it's easy to inspect the > > state of that guest and avoid to schedule away when it was interrupted > > in a spinlock held section. That guest/host shared state needs to be > > On a large system under high contention sleeping can perform surprisingly > well. pthread mutexes have a tendency to beat kernel spinlocks there. > So avoiding sleeping locks completely (that is what pv locks are > essentially) is not necessarily that good. Care to back that up with numbers and proper trace evidence instead of handwaving? I've stared at RT traces and throughput problems on _LARGE_ machines long enough to know what I'm talking about and I can provide evidence in a split second. > Your proposal is probably only a good idea on low contention > and relatively small systems. Sigh, you have really no fcking clue what you are talking about. On RT we observed scalabilty problems way before hardware was available to expose them. So what's your point? Put up or shut up, really! tglx