Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932104AbVJCBSV (ORCPT ); Sun, 2 Oct 2005 21:18:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932106AbVJCBSV (ORCPT ); Sun, 2 Oct 2005 21:18:21 -0400 Received: from mx1.redhat.com ([66.187.233.31]:43197 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932104AbVJCBSV (ORCPT ); Sun, 2 Oct 2005 21:18:21 -0400 Date: Sun, 2 Oct 2005 21:18:16 -0400 (EDT) From: Rik van Riel X-X-Sender: riel@cuia.boston.redhat.com To: Luke Kenneth Casson Leighton cc: "Martin J. Bligh" , linux-kernel@vger.kernel.org Subject: Re: what's next for the linux kernel? In-Reply-To: <20051003011041.GN6290@lkcl.net> Message-ID: References: <20051002204703.GG6290@lkcl.net> <20051002230545.GI6290@lkcl.net> <54300000.1128297891@[10.10.2.4]> <20051003011041.GN6290@lkcl.net> 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: 867 Lines: 24 On Mon, 3 Oct 2005, Luke Kenneth Casson Leighton wrote: > well... actually, as it turns out, the l4linux and l4ka people have > already done most of the work!! And I am sure they have reasons for not submitting their changes to the linux-kernel mailing list. They probably know something we (including you) don't know. Switching out the low level infrastructure does NOT help with scalability. The only way to make the kernel more parallelizable is by changing the high level code, ie. Linux itself. Adding a microkernel under Linux is not going to help with anything you mentioned so far. -- All Rights Reversed - 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/