Date: Wed, 14 May 2003 18:25:26 -0700
From: Andrew Morton <akpm@digeo.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: ch@murgatroid.com, inaky.perez-gonzalez@intel.com, hch@infradead.org,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.68 FUTEX support should be optional
Message-Id: <20030514182526.36823e2b.akpm@digeo.com>
In-Reply-To: <Pine.LNX.4.44.0305141758070.28007-100000@home.transmeta.com>
References: <001c01c31a7c$327cc350$175e040f@bergamot>
	<Pine.LNX.4.44.0305141758070.28007-100000@home.transmeta.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1085
Lines: 29

Linus Torvalds <torvalds@transmeta.com> wrote:
>
> And do you guys actually use a recent glibc snapshot? Do you ever expect 
>  to?

I believe this effort is more targetted at teeny little embedded gadgets -
devices which are very remote from workstations, desktops and servers.

Presumably the people who are programming such gadgets will know if they
need futexes or not.


We've never clearly addressed the issue of just how far the mainstream
kernel should scale down, and how pluggable the various kernel components
should be.

Retrofitting pluggability is hard (CONFIG_BLOCK_LAYER) but at the very
least, we should make this effort for newly-added components.


Assuming, of course, that we _do_ want to make the mainstream kernel scale
that far down.  It could be argued that this is a role for vendors or other
specialised parties.

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