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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!sei!ajpo!falis
From: falis@ajpo.sei.cmu.edu (Edward Falis)
Newsgroups: comp.lang.ada
Subject: Re: Interactive I/O in Ada
Summary: Non-blocking I/O
Message-ID: <652@ajpo.sei.cmu.edu>
Date: 24 Jan 90 18:12:42 GMT
References: <9001232125.AA09245@monolith.>
List-Id: <comp.lang.ada>

Without getting too commercial here, your best bet on this issues is to
check with the vendor. Several vendors do provide this facility: a task
about to block on an I/O operation relinquished the processor so another
task caN be scheduled.  This is actually fairly trivial to implement
when an Ada task directly issues the I/O operation request. Where it
gets more interesting is when an Ada task calls interfaced code
(EG third party software) which issues an I/O call which will block.

ps most Ada systems intended for use on bare targets include an
"Ada OS" 	- Ed Falis, Alsys Inc.