From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758899Ab2CHW1s (ORCPT ); Thu, 8 Mar 2012 17:27:48 -0500 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:10449 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753889Ab2CHW1r (ORCPT ); Thu, 8 Mar 2012 17:27:47 -0500 X-Authority-Analysis: v=2.0 cv=Wf+OmjdX c=1 sm=0 a=ZycB6UtQUfgMyuk2+PxD7w==:17 a=XQbtiDEiEegA:10 a=5SG0PmZfjMsA:10 a=Q9fys5e9bTEA:10 a=97dKWPFg1Ekkxx0hFV8A:9 a=og_ouKvnIfdgG3lbXBoA:7 a=PUjeQqilurYA:10 a=ZycB6UtQUfgMyuk2+PxD7w==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.80.29 Message-ID: <1331245665.25686.521.camel@gandalf.stny.rr.com> Subject: Re: [ANNOUNCE] 3.2.9-rt17 From: Steven Rostedt To: Peter Zijlstra Cc: Thomas Gleixner , LKML , linux-rt-users Date: Thu, 08 Mar 2012 17:27:45 -0500 In-Reply-To: <1331245213.11248.446.camel@twins> References: <1331230991.25686.452.camel@gandalf.stny.rr.com> <1331231287.11248.396.camel@twins> <1331232159.25686.456.camel@gandalf.stny.rr.com> <1331235579.11248.402.camel@twins> <1331237441.25686.469.camel@gandalf.stny.rr.com> <1331238369.11248.426.camel@twins> <1331240882.25686.499.camel@gandalf.stny.rr.com> <1331241627.11248.430.camel@twins> <1331241940.25686.502.camel@gandalf.stny.rr.com> <1331242104.11248.432.camel@twins> <1331242574.25686.505.camel@gandalf.stny.rr.com> <1331242625.11248.433.camel@twins> <1331243078.25686.510.camel@gandalf.stny.rr.com> <1331243642.11248.441.camel@twins> <1331244812.25686.518.camel@gandalf.stny.rr.com> <1331245213.11248.446.camel@twins> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.2.2-1 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2012-03-08 at 23:20 +0100, Peter Zijlstra wrote: > and with rt-mutex having the equal priority lock stealing this reverts > to a plain test-and-set lock. There's only a tiny window in which A can > actually get the lock and that is hampered by B's cpu owning the > cacheline in exclusive mode. > > I simply cannot see guaranteed progress here. This can be easily fixed by not having the lateral steal when a lock has a priority. -- Steve