Re: Ada 95 tasking problems with Ada 83 code

["Pat Rogers" <progers@NOclasswideSPAM.com>]

"Richard Riehle" <laoXhai@ix.netcom.com> wrote in message
news:39AF2DEC.71D8B897@ix.netcom.com...

<snip>

> Reminder:  you still need to take a look at RMA if you have 100
concurrent tasks.

I confess I don't see why.  Surely the number of tasks, by itself,
doesn't require a schedulability analysis.  (There may very well be
deadlines associated, but that hasn't been indicated as far as I
know.)  Absent deadlines, then this is "just" a concurrent program, in
which case the issues are maximizing throughput and ensuring liveness.
Liveness isn't a function of the number of tasks, so I don't see the
connection.

On the other hand, let's say there are deadlines.  In that case, a
static-priority preemptive scheduling scheme may not be the right
approach (e.g., RMA).  Perhaps a dynamic scheme might be best -- say
Earliest Deadline First (which is optimal too).  In other words, it
seems to me that that the info so far -- 100 tasks -- isn't sufficient
to require use of any schedulability analysis, RMA or otherwise.

(Sure, the more tasks one has the more likely a general-purpose
tasking system is to bog down, but that is a separate issue I would
think.)

Of course you know these things, so what am I missing?

---
Patrick Rogers                      Consulting and Training in:
http://www.classwide.com      Deadline Schedulability Analysis
progers@classwide.com        Software Fault Tolerance
(281)648-3165                       Real-Time/OO Languages

Adam ... does not deserve all the credit; much is due to Eve, the
first woman, and Satan, the first consultant.
Mark Twain