Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759027AbYFYPZp (ORCPT ); Wed, 25 Jun 2008 11:25:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756709AbYFYPZK (ORCPT ); Wed, 25 Jun 2008 11:25:10 -0400 Received: from gateway-1237.mvista.com ([63.81.120.158]:40827 "EHLO gateway-1237.mvista.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755629AbYFYPZI (ORCPT ); Wed, 25 Jun 2008 11:25:08 -0400 Subject: Re: [PATCH 6/6] futex: fix miss ordered wakeups From: Daniel Walker To: Peter Zijlstra Cc: linux-kernel@vger.kernel.org, Thomas Gleixner In-Reply-To: <1214406451.24356.13.camel@lappy.programming.kicks-ass.net> References: <20080624232018.817822790@mvista.com> <20080624232020.505470899@mvista.com> <1214371767.16881.5.camel@twins> <1214404611.21035.20.camel@localhost.localdomain> <1214406451.24356.13.camel@lappy.programming.kicks-ass.net> Content-Type: text/plain Date: Wed, 25 Jun 2008 08:25:07 -0700 Message-Id: <1214407507.21035.32.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1681 Lines: 43 On Wed, 2008-06-25 at 17:07 +0200, Peter Zijlstra wrote: > On Wed, 2008-06-25 at 07:36 -0700, Daniel Walker wrote: > > On Wed, 2008-06-25 at 07:29 +0200, Peter Zijlstra wrote: > > > > > Daniel, I'm not sure what to think,.. you were told how broken this > > > approach was, you were told to give proper justification for this > > > change. You did neither and just reposted the same old broken shite > > > again. > > > > Broken approach ? Never heard that before, > > I suggest you re-read some of Thomas' emails from last time... > > http://lkml.org/lkml/2008/6/12/275 Most of what he's saying there is that it breaks real time, and I provided a real time fix in this set of patches. I don't have a problem with the state mixing, since 99.9% of the time we're dealing operations that don't interact (and it's perfectly ok when they do interact). > > in fact the problem is > > whether or not the changes are needed (not weather their broken).. I > > gave justification in the last thread, and I'm not sure why it's unclear > > to you.. > > You failed to convince, also justification goes in the changelog, not in > random lkml threads. It boils down to POSIX compliance which was discussed in the last thread. POSIX requires the waiters to be sorts for 5-10 different API's which ultimately use the futex (most of which aren't at all related to PI). And yes I can add it to the headers, before it goes up stream. Daniel -- 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/