Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263818AbTETP3p (ORCPT ); Tue, 20 May 2003 11:29:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263823AbTETP3p (ORCPT ); Tue, 20 May 2003 11:29:45 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:23047 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id S263818AbTETP3o (ORCPT ); Tue, 20 May 2003 11:29:44 -0400 Date: Tue, 20 May 2003 08:41:53 -0700 (PDT) From: Linus Torvalds To: Christoph Hellwig cc: Ingo Molnar , Rusty Russell , Ulrich Drepper , Subject: Re: [patch] futex requeueing feature, futex-requeue-2.5.69-D3 In-Reply-To: <20030520075627.A28002@infradead.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1262 Lines: 30 On Tue, 20 May 2003, Christoph Hellwig wrote: > > Actually it should go away before 2.6.0. sys_futex never was part of a > released stable kernel so having the old_ version around is silly. That's not a valid argument. That's an _excuse_. Guys, binary compatibility is important. It's important enough that if something got extensively used on development kernels, it's _still_ a hell of a lot more important than most other things around. The _only_ things that trump binary compatibility are - developer sanity (ie it has to be truly mindbogglingly hard to support the old interface) - stability (ie if the old interface was so badly designed that it can't be done right - mmap on /proc//mem was one of these). - it's been deprecated over at least one full stable release. Something like "it's only been in the development kernels" is simply not an issue. The only thing that matters is whether it is used by various binaries or not. And I think futexes are used a lot by glibc.. Linus - 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/