Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932075AbVJBVF6 (ORCPT ); Sun, 2 Oct 2005 17:05:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932076AbVJBVF6 (ORCPT ); Sun, 2 Oct 2005 17:05:58 -0400 Received: from mx1.redhat.com ([66.187.233.31]:59847 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932075AbVJBVF6 (ORCPT ); Sun, 2 Oct 2005 17:05:58 -0400 Date: Sun, 2 Oct 2005 17:05:42 -0400 (EDT) From: Rik van Riel X-X-Sender: riel@cuia.boston.redhat.com To: Luke Kenneth Casson Leighton cc: linux-kernel@vger.kernel.org Subject: Re: what's next for the linux kernel? In-Reply-To: <20051002204703.GG6290@lkcl.net> Message-ID: References: <20051002204703.GG6290@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: 744 Lines: 21 On Sun, 2 Oct 2005, Luke Kenneth Casson Leighton wrote: > and, what is the linux kernel? > > it's a daft, monolithic design that is suitable and faster on > single-processor systems, and that design is going to look _really_ > outdated, really soon. Linux already has a number of scalable SMP synchronisation mechanisms. The main scalability effort nowadays is about the avoidance of so-called "cache line bouncing". http://wiki.kernelnewbies.org/wiki/SMPSynchronisation -- 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/