From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Nikita V. Youshchenko" Subject: Re: preempt rt in commercial use Date: Tue, 14 Sep 2010 18:30:02 +0400 Message-ID: <201009141830.03206@zigzag.lvk.cs.msu.su> References: <20100914094411.GB10841@pengutronix.de> <4C8F8500.5070002@theptrgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Robert Schwebel , Raz , linux-rt-users To: Jeff Angielski Return-path: Received: from gate.lvk.cs.msu.su ([158.250.17.1]:49054 "EHLO mail.lvk.cs.msu.su" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750932Ab0INOaF (ORCPT ); Tue, 14 Sep 2010 10:30:05 -0400 In-Reply-To: <4C8F8500.5070002@theptrgroup.com> Content-Disposition: inline Sender: linux-rt-users-owner@vger.kernel.org List-ID: > >> anyone can say preempt rt is hard real time? > > > > Hard realtime has something to do with how you define "missing the > > deadline". If somebody cuts the cable of your roboter controller in > > the factory hall, the system misses the deadline. So it is all about > > probabilities: hard realtime systems have a very, very low probability > > of missing the deadline. However, in real life systems, it is> 0%. > > > > So yes, if you talk about real world, it is hard realtime. > > No. Preempt rt it's not hard realtime. > > But most people/companies who think they need hard realtime really > don't. They can live with soft realtime and have a really low > probability of missing deadlines and having long latencies. For these > people, the preempt rt is adequate. Isn't any case where preempt-rt does not behave as hard reatlime a bug in preempt-rt, that should be reported to this list and eventually fixed?