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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,67c50b972ca3b532 X-Google-Attributes: gid103376,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: Realtime Ada Conferences Date: 1996/03/27 Message-ID: #1/1 X-Deja-AN: 144498686 references: <4j9j9f$620@hacgate2.hac.com> <4jadve$pcq@news.sei.cmu.edu> organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1996-03-27T00:00:00+00:00 List-Id: Larry said " >Is anything being done to allow Ada compiler vendors to >produce compilers that have task context switch times >in the 20 us range? It seems that most compiler vendors >are not able to comply with the Ada83 tasking model >and provide realtime context switching capabilities. Yes, they're called faster computers. :-) Seriously, the implication I got from what you said is that Ada compilation systems without 20 usec context switching times do not provide realtime context switching capabilities. Many realtime applications do not require this level of performance and are nonetheless realtime. "Realtime" implies to me predictable timing behavior, and not some arbitrary level of performance." Actually more and more realtime systems are being built on top of so-called real-time systems like NT, Lynx, Chorus, or even just Vanilla unix with Posix interfaces. I say "so-called", because if your idea of real-time is 20 microsecond context switch (*) then you will find that the OS already has lost the battle by a significant factor. But, as Larry said, applications can certainly be real-time without requiring 20 usec cst. (*) 20 usec seems slow to me, when I was writing real-time operating systems for Honeywell on 4MHz 8080 systems, we were aiming at better context switching times than this :-)