Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261483AbVE3Ley (ORCPT ); Mon, 30 May 2005 07:34:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261468AbVE3Lex (ORCPT ); Mon, 30 May 2005 07:34:53 -0400 Received: from lirs02.phys.au.dk ([130.225.28.43]:62132 "EHLO lirs02.phys.au.dk") by vger.kernel.org with ESMTP id S261478AbVE3Len (ORCPT ); Mon, 30 May 2005 07:34:43 -0400 Date: Mon, 30 May 2005 13:34:00 +0200 (METDST) From: Esben Nielsen To: Nick Piggin Cc: kus Kusche Klaus , James Bruce , "Bill Huey (hui)" , Andi Kleen , Sven-Thorsten Dietrich , Ingo Molnar , dwalker@mvista.com, hch@infradead.org, akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: RT patch acceptance In-Reply-To: <429AEE3A.5080803@yahoo.com.au> 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: 1717 Lines: 40 On Mon, 30 May 2005, Nick Piggin wrote: > kus Kusche Klaus wrote: > > >>You don't explain how making the Linux kernel hard-RT > >>will be so much simpler and more supportable! > > > > > > I didn't state that a hard-RT linux is simpler, technically > > (however, personally, I believe that once RT linux is there, *our* > > job of writing RT applications, device drivers, ... will be simpler > > compared to a nanokernel approach). > > > > Perhaps very slightly simpler. Let's keep in mind that we're > not talking about "hello, world" apps here though, so I don't > think such a general statement is of any use. > One important aspect: Time to marked. Linux does have good hardware support compared to commercial RTOSs and guest kernels! I.e. if you can use the native Linux driver you very soon has your board up and running. On the other hand if you first have to write and debug (or buy) drivers for your RTOS or guest kernel you are already delayed for months. I do like the idea of guest kernels - especially the ability to enforce a strict seperation of RT and non-RT. But you can't use _any_ part of the Linux kernel in your RT application - not even drivers. I know a lot of stuff in Linux wont ever be useable as it is highly non-deterministic (the file system forinstance); but some of it might turn up to become deterministic (enough :-) once people start to work on it with that ind mind - the network stack would be a good place to start.... Esben - 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/