Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!inmos.co.uk!malc
From: malc@inmos.co.uk (Malcolm Boffey)
Newsgroups: comp.sys.transputer
Subject: Re: low priority processes
Message-ID: <13468.8905301926@wraxall.inmos.co.uk>
Date: 30 May 89 19:26:22 GMT
References: <1062@wacsvax.OZ>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: INMOS Limited, Bristol, UK.
Lines: 12

When a process timeslices, it is put onto the back of the relevant
(low priority) queue, even if the queue was empty. The first process (which may
of course be the same as what was just running) is then taken off the queue and
scheduled. If the empty queue was treated as a special case, it would save
about 0.1%, while costing more microcode and hence space.

\input {stddisclaimer.tex}
-- 
 Malcolm Boffey, Transputer Group, Inmos.   | Inmos Ltd,
email: malc@inmos.co.uk                     | 1000 Aztec West, Almondsbury,
JANET: MALC@UK.CO.INMOS                     | Brisol BS12 4SQ. 
UUCP:  ...uunet!mcvax!ukc!inmos!malc        | Tel. +44 454 616616 x530