From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 14 Aug 91 15:24:13 GMT
From: torolab4.vnet.ibm.com!jrussell@ucbvax.Berkeley.EDU
Subject: Re: Ada and Unix--Blocked Tasks
Message-ID: <9108141524.AA09403@ucbvax.berkeley.edu>
List-Id: <comp.lang.ada>

Mike Feldman asks if any vendors map Ada tasks onto OS processes.
The IBM compiler for MVS has a pragma, OS_TASK, that does this for a
task or task type, and some form parameters that control
synchronous/asynchronous I/O.  (This is the same compiler Bob Kitzberger
mentioned.)  People who want to do real-timish things typically use the
pragma, because MVS task scheduling is pretty fair.  There are some
additional hooks into MVS tasking, such as a priority for MVS subtasks
distinct from the Ada priority, and ways to minimize the overhead of OS
task creation/termination.

The same pragma is part of the IBM RISC System/6000 compiler, using
the AIX shared memory features.

The approach does have some possible disadvantages, like more expensive
context switching, but people who need the extra capability are generally
positive.

John
(Representing myself only.)