From: "Christopher Hoover" <ch@murgatroid.com>
To: "'Linus Torvalds'" <torvalds@transmeta.com>,
       "'Ulrich Drepper'" <drepper@redhat.com>
Cc: "'Dave Jones'" <davej@codemonkey.org.uk>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] 2.5.68 FUTEX support should be optional
Date: Wed, 14 May 2003 17:58:11 -0700
Organization: Murgatroid.Com
Message-ID: <002201c31a7d$0f3f32a0$175e040f@bergamot>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.LNX.4.44.0305141246180.27329-100000@home.transmeta.com>
Importance: Normal
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1221
Lines: 35


> I don't see the point in dropping futexes except
> perhaps in a very controlled embedded environment,
> but if that is the case,  then a PC config 
> should just force it to "y" and not even ask the user. 

We could do this (et al) under CONFIG_TINY, if you would prefer.


> We absolutely do NOT want the situation where
> a program will not work just because the user forgot
> some config option that mostly isn't needed.

This a specious argument.  There are many ways one can configure a
kernel that will make it fail to boot or run user space properly.
There's no getting around knowing what it is your configuring in and
out.

Note that I set the default to Y.  I also agree that I could have been
more verbose in the help string.

> And futexes _are_ going to be needed. Any sane high-performance
threading 
> implementation _will_ use them. No ifs, buts or maybe's.

All big machines, sure.  All small machines, it depends.  All the (user)
world is not glibc.

-ch

-
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/