Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753806AbbFILVz (ORCPT ); Tue, 9 Jun 2015 07:21:55 -0400 Received: from casper.infradead.org ([85.118.1.10]:50038 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753505AbbFILVs (ORCPT ); Tue, 9 Jun 2015 07:21:48 -0400 Date: Tue, 9 Jun 2015 13:21:42 +0200 From: Peter Zijlstra To: Thomas Gleixner Cc: Davidlohr Bueso , Ingo Molnar , Steven Rostedt , Mike Galbraith , "Paul E. McKenney" , Sebastian Andrzej Siewior , linux-kernel@vger.kernel.org Subject: Re: [PATCH -rfc 4/4] locking/rtmutex: Support spin on owner (osq) Message-ID: <20150609112142.GU3644@twins.programming.kicks-ass.net> References: <1432056298-18738-1-git-send-email-dave@stgolabs.net> <1432056298-18738-5-git-send-email-dave@stgolabs.net> <1433824902.3165.61.camel@stgolabs.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 706 Lines: 15 On Tue, Jun 09, 2015 at 11:29:59AM +0200, Thomas Gleixner wrote: > > If you look at the RT code, then you'll notice that in the slow lock > path we queue the incoming waiter (including the PI dance) and then > spin only if the waiter is the top waiter on the lock. On a related note; does the RT code still add lock stealing to rtmutex? We allow higher prio lock stealing, but I seem to remember a longish debate if we should allow equal prio lock stealing. -- 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/