From: eachus@spectre.mitre.org (Robert I. Eachus)
Subject: Re: Ada Task priorities
Date: 1997/01/28
Date: 1997-01-28T00:00:00+00:00 [thread overview]
Message-ID: <EACHUS.97Jan27210405@spectre.mitre.org> (raw)
In-Reply-To: dewar.854313404@merv
In article <dewar.854313404@merv> dewar@merv.cs.nyu.edu (Robert Dewar) writes:
>> Can one guarantee that if all 3 tasks are eligible for execution
>> at the same time, that task a will finish it's work before
>> task b begins to run, and task c will only run after both
>> tasks a and b finish? (Assuming no tasks rendezvous with
>> other tasks during this time?)
>> I suppose even OS calls would make this highly platform dependent.
> Of course not, think multiprocessors for a moment!
Quite correct. There is another case to keep in mind. If task a and
b read from disk, it is perfectly legitimate (in Ada 83 or 95) for c
to run while waiting for the I/O to complete. This is usually a
special case of multiprocessing, but one most people overlook in
desktop systems. (In embedded systems, I/O latencies are carefully
calculated and there is unlikely to be any disk I/O of any kind. ;-)
In Ada it is possible to cover all the bases and get predicable
tasking behavior, but in modern systems you really have to understand
the underlying hardware design.
--
Robert I. Eachus
with Standard_Disclaimer;
use Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...
next prev parent reply other threads:[~1997-01-28 0:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-26 0:00 Ada Task priorities Kevin Radke
1997-01-26 0:00 ` Jonathan Polley
1997-01-27 0:00 ` Geert Bosch
1997-01-26 0:00 ` Robert Dewar
1997-01-28 0:00 ` Robert I. Eachus [this message]
1997-01-27 0:00 ` Geert Bosch
1997-01-27 0:00 ` Michael F Brenner
1997-01-28 0:00 ` Kevin Radke
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox