From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261507AbVFAX7k (ORCPT ); Wed, 1 Jun 2005 19:59:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261522AbVFAX63 (ORCPT ); Wed, 1 Jun 2005 19:58:29 -0400 Received: from smtp.lnxw.com ([207.21.185.24]:11524 "EHLO smtp.lnxw.com") by vger.kernel.org with ESMTP id S261518AbVFAX4G (ORCPT ); Wed, 1 Jun 2005 19:56:06 -0400 Date: Wed, 1 Jun 2005 16:59:32 -0700 To: Bill Huey Cc: Andrea Arcangeli , Esben Nielsen , Thomas Gleixner , Karim Yaghmour , Ingo Molnar , Paulo Marques , "Paul E. McKenney" , James Bruce , Nick Piggin , Andi Kleen , Sven-Thorsten Dietrich , dwalker@mvista.com, hch@infradead.org, akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: RT patch acceptance Message-ID: <20050601235932.GA12613@nietzsche.lynx.com> References: <20050601195905.GX5413@g5.random> <20050601201754.GA27795@nietzsche.lynx.com> <20050601203212.GZ5413@g5.random> <20050601204612.GA27934@nietzsche.lynx.com> <20050601210716.GB5413@g5.random> <20050601214257.GA28196@nietzsche.lynx.com> <20050601215913.GB28196@nietzsche.lynx.com> <20050601223250.GH5413@g5.random> <20050601230244.GA11262@nietzsche.lynx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050601230244.GA11262@nietzsche.lynx.com> User-Agent: Mutt/1.5.9i From: Bill Huey (hui) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 01, 2005 at 04:02:44PM -0700, Bill Huey wrote: > This is not the purpose of the patch, nor will it ever be. RT apps don't > depend on this property as was previously mentioned in this thread. ... > Again, this has been covered previously by this thread. It's ultimately > about writing RT apps that have a more sophisticated use that RTAI or > RT Linux. Andrea, I mean those above comments to be hard RT. I do mention a syscall use and expression of these RT properties, but it's really not hard RT but something else closer to soft RT threads. I blew it by using the wrong definition there. They still all have to interact with each other in a temporarly protected way so that latency is propagated through each RT domain (soft, hard, none) in the app. bill