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
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!gryphon!pnet02!bagpiper
From: bagpiper@pnet02.gryphon.com (Michael Hunter)
Newsgroups: comp.lang.ada
Subject: Fixed Frame Scheduling
Message-ID: <23041@gryphon.COM>
Date: 4 Dec 89 06:20:25 GMT
Sender: root@gryphon.COM
Organization: People-Net [pnet02], Redondo Beach, CA.
List-Id: <comp.lang.ada>

I have been implementing a fixed frame scheduler in Ada.  I had initially
planned (note for TH: designed) to do the context switches in some assembly
glue.  This was mainly due to the fact that I didn't feel comfortable enought
with Ada tasking to get the job done in time..I thought.  But after reading
some more in the LRM and Cohen I think I almost see a way.  If anyone has any
hints please send them to me.

(What I mean by fixed frame scheduler is the ability to start the execution of
a task for some predetermined amount of time, and then cut it off.  This looks
like round robin scheduling with very well defined time slices.  I just havn't
figured out how to allow the calling task to get control back from the
acceptor.)

I am working on a vax under VMS and will be running this program at the
highest priority...so I shouldn't have too much problem ensuring that it gets
a lot of CPU.  I would entertain solutions that use features specific to VMS
or specific to VAX Ada...but I would rather see a clean, portable, Ada
solution.

                                Michael

Mike Hunter - Box's and CPU's from HELL: iapx80[012]86, PR1ME 50 Series, 1750a
UUCP: {ames!elroy, <routing site>}!gryphon!pnet02!bagpiper
INET: bagpiper@pnet02.gryphon.com