Re: low priority processes

Article View: comp.sys.transputer

Article #2691

Back to comp.sys.transputer Previous Next

#2691

From: Peter Dodd
Date: Sat, 20 May 1989 09:35

17 lines
982 bytes

Sorry for the repost...

>  Given a low priority process executing alone :
>
>> The question is...(if my assumptions are correct?!), what is the time
>> interval between the process being de-activated and it becoming active 
>> again. Not very much, I (again) assume. 
>
>  Im not sure, but it will be one of two cases :

Of course it will be neither, since both FPtr1, and BPtr1 will be NULL.
As they point to workspaces that are active awaiting execution, excluding
the currently executing process. Hence descheduling cannot occur.

Peter.
----------------
peter@wacsvax.oz

Technical Details

Message-ID: <1065@wacsvax.OZ>

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!munnari!uniwa!wacsvax!peter

References: <789@uowcsa.cs.uow.oz> <1062@wacsvax.OZ>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!munnari!uniwa!wacsvax!peter
From: peter@wacsvax.OZ (Peter Dodd)
Newsgroups: comp.sys.transputer
Subject: Re: low priority processes
Summary: Getting warmer...
Keywords: transputers
Message-ID: <1065@wacsvax.OZ>
Date: 20 May 89 09:35:18 GMT
References: <789@uowcsa.cs.uow.oz> <1062@wacsvax.OZ>
Organization: Comp Sci, Uni. Western Australia.
Lines: 17

Reply to Parent Message