Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261821AbVEaCSy (ORCPT ); Mon, 30 May 2005 22:18:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261739AbVEaCSy (ORCPT ); Mon, 30 May 2005 22:18:54 -0400 Received: from mustang.oldcity.dca.net ([216.158.38.3]:21456 "HELO mustang.oldcity.dca.net") by vger.kernel.org with SMTP id S261821AbVEaCSs (ORCPT ); Mon, 30 May 2005 22:18:48 -0400 Subject: Re: RT patch acceptance From: Lee Revell To: James Bruce Cc: Nick Piggin , "Bill Huey (hui)" , Andi Kleen , Sven-Thorsten Dietrich , Ingo Molnar , dwalker@mvista.com, hch@infradead.org, akpm@osdl.org, linux-kernel@vger.kernel.org In-Reply-To: <429BA27A.5010406@andrew.cmu.edu> References: <1117044019.5840.32.camel@sdietrich-xp.vilm.net> <20050526193230.GY86087@muc.de> <1117138270.1583.44.camel@sdietrich-xp.vilm.net> <20050526202747.GB86087@muc.de> <4296ADE9.50805@yahoo.com.au> <20050527120812.GA375@nietzsche.lynx.com> <429715DE.6030008@yahoo.com.au> <20050527233645.GA2283@nietzsche.lynx.com> <4297EB57.5090902@yahoo.com.au> <20050528054503.GA2958@nietzsche.lynx.com> <42981467.6020409@yahoo.com.au> <4299A98D.1080805@andrew.cmu.edu> <429ADEDD.4020805@yahoo.com.au> <429B1898.8040805@andrew.cmu.edu> <429B2160.7010005@yahoo.com.au> <429BA27A.5010406@andrew.cmu.edu> Content-Type: text/plain Date: Mon, 30 May 2005 22:06:44 -0400 Message-Id: <1117505204.22167.11.camel@mindpipe> Mime-Version: 1.0 X-Mailer: Evolution 2.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1351 Lines: 34 On Mon, 2005-05-30 at 19:32 -0400, James Bruce wrote: > This is sort of confused > by the fact that Ingo called it "hard realtime" because he measured a > maximum latency during a stress test. Unfortunately that's not > really > hard realtime if you are just measuring it; Rather its "really damn > good > soft realtime". An analysis of code paths could be done to determine > if > something really does satisfy hard-RT constraints, but to my > knowledge > that's not on the table at this point. So you're discussing soft > realtime if you're dicussing the RT patch. > > So its really just a misunderstanding No, *you're* the one misunderstanding. Since *everything* is preemptible except a few known code paths whose execution times determine the maximum possible latency from interrupt to running the highest priority user process. That's the determinism, no more, no less. But some people inexplicably think this thread is about providing deterministic hard RT performance for some subset of system calls, or disk IO or something, none of which have anything to do with PREEMPT_RT. Lee - 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/