Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think!snorkelwacker!apple!netcom!schang
From: schang@netcom.UUCP (Sehyo Chang)
Newsgroups: comp.realtime
Subject: Re: Why concurrency in real-time systems design?
Message-ID: <8156@netcom.UUCP>
Date: 1 Mar 90 22:32:08 GMT
References: <1990Mar1.152922.1005@axion.bt.co.uk>
Organization: NetCom- The Bay Area's Public Access Unix System {408 249-0290 guest}
Lines: 32

In article <1990Mar1.152922.1005@axion.bt.co.uk> rdoyle@axion.bt.co.uk (Number Six) writes:
>
> Another question for all you real-time experts...
>
> Can anyone give me any ideas/references on why you need
>to use concurrent tasks in the design of real-time systems?
>I am perfectly willing to accept arguments based on purely
>pragmatic reasons (eg "Past experience shows this is the
>best way"), but I would be interested to hear any fundamental
>justifications that this is the way we should model the design 
>of any real-time system. 
>
> (Please note that I am not assuming a concurrent hardware
>architecture - the design could, for example, be implemented
>on a single processor).
>				Richard Doyle
>
>--
Simple, it is easier to design natural world with concurrent system than
with serial design (even if you do everything in one processor, then you
want to parallel-serial transformer or time slice scheduler). Summarize
you want(and should) do concurrent design for you real time system because
(1) multiple concurrent system gives better performance than a single   
   processor.  It is easier to distribute load among concurrent processes
   for time-critical event
(2) concurrent design are easier than serial design in addition to the fact
    much of system specification/design can be only done in concurrently!!.

-- 
Sehyo Chang						schang@netcom.uucp
Ascent Logic Corp.
(408)943-0630