* Forcing context switches (was: Ada Tasking problem)
@ 1991-11-26 16:50 cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think.com!hsdndev!encore!max
0 siblings, 0 replies; only message in thread
From: cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think.com!hsdndev!encore!max @ 1991-11-26 16:50 UTC (permalink / raw)
> [various discussion about using delays, especially delay 0.0, to force
> context switches deleted]
The Encore parallel runtime ignores delays of 0.0. Of course, since this
runtime is for a multiprocessor, the issue of context switches is a bit more,
um, "interesting." The vanilla Unix implementation maps each Ada task to
(essentially) a kernel thread, so Unix handles the timeslicing. The realtime
implementation uses a combination of priority and runtime-established
timeslice parameters to do timeslicing.
It would be nice to have some guidance from AJPO or someplace
regarding what runtime tuning knobs are expected to be available.
But then, maybe that's what "market differentiation" is all about. :-)
-- Jerry Callen
jcallen@world.std.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1991-11-26 16:50 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1991-11-26 16:50 Forcing context switches (was: Ada Tasking problem) cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think.com!hsdndev!encore!max
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox