From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f569d,7d68662d79c59f1c
X-Google-Attributes: gidf569d,public
X-Google-Thread: 109fba,46882e3fad98420e
X-Google-Attributes: gid109fba,public
X-Google-Thread: 1108a1,9292211c2d4756a8
X-Google-Attributes: gid1108a1,public
X-Google-Thread: 102b75,7d68662d79c59f1c
X-Google-Attributes: gid102b75,public
X-Google-Thread: 103376,7d68662d79c59f1c
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-12-31 10:23:27 PST
Path: 
 nntp.gmd.de!Germany.EU.net!howland.reston.ans.net!news.sprintlink.net!redstone.interpath.net!ddsw1!news.rtd.com!dgy
From: dgy@rtd.com (Don Yuniskis)
Newsgroups: comp.lang.c++,comp.object,comp.arch,comp.multimedia,comp.lang.ada
Subject: Re: What's Real-Time? (was Re: Widespread C++ Competency Gap?)
Date: 31 Dec 1994 02:12:29 GMT
Organization: RTD Internet Access
Message-ID: <3e2emd$6fd@baygull.rtd.com>
References: <787227087snz@wslint.demon.co.uk> <3e22hi$pqf@baygull.rtd.com>
 <3e26mc$n9u@Starbase.NeoSoft.COM> <hbaker-3012941712040001@192.0.2.1>
NNTP-Posting-Host: seagull.rtd.com
Xref: nntp.gmd.de comp.lang.c++:84617 comp.object:19060 comp.arch:27393
 comp.multimedia:25694 comp.lang.ada:17714
Date: 1994-12-31T02:12:29+00:00
List-Id: <comp.lang.ada>

In article <hbaker-3012941712040001@192.0.2.1>,
Henry Baker <hbaker@netcom.com> wrote:

>In the RT community there are the terms '_hard_ real-time' and
>'_soft_ real-time'.  'Hard' RT means that the consequences of missing
>a deadline are catastrophic, while 'soft' RT means that the consequences
>are expensive, but not catastrophic.

Yes, as I indicated in my reference to the value function associated
with the missed deadline (for t>deadline, value <= 0 for HRT; value > 0
for SRT).

>Designing for a 'hard' RT system is different from designing for a
>'soft' RT system because you have to find the latencies of _every_
>operation, no matter how rare -- e.g., you have to worry about the
>latencies of rare combinations of rare events -- e.g., multiple page
>faults from a single instruction, cache faults for every memory reference
>of a 1000-instruction sequence, etc.

Exactly!  A fact that most designers neglect either from ignorance or
by choice (it's orders of magnitude harder to design for the worst-case
whether you're designing hardware OR software -- tho', admittedly, a
worst-case hardware design is orders of magnitude EASIER than a
worst-case software design ;-) :-(

>This means that nearly everyone is looking for ways to convert 'hard'
>RT systems into 'soft' RT systems so that they can take advantage of
>the increased average speeds.
>
>So if you're still doin' 'hard time', wise up!  :-) :-)

Right.  However, certain parts of evry application "must" be HRT.
The trick is to move as much of the application into the domain of
SRT -- "Gee, it would be real nice if this got done on time... but
it's more important that I know how to deal with the consequences
of when it DOESN'T get done on time!"