Re: low priority processes

Article View: comp.sys.transputer

Article #2690

Back to comp.sys.transputer Previous Next

#2690

From: Peter Dodd
Date: Sat, 20 May 1989 04:49

23 lines
1112 bytes


Ian,
  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 :

1) The processor deschedules the process then reschedules the process
   who's workspace is pointed to by the FPtr1 register, which will take 
   less than 1us. ( Normal context switch time )

2) The processor will recognise that the FPtr1 and current Workspace
   registers are identical, and continue execution without descheduling.
   Even less time than context switching. 

Peter.

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

Technical Details

Message-ID: <1062@wacsvax.OZ>

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

References: <789@uowcsa.cs.uow.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: What does it do ?
Keywords: transputers
Message-ID: <1062@wacsvax.OZ>
Date: 20 May 89 04:49:35 GMT
References: <789@uowcsa.cs.uow.oz>
Organization: Comp Sci, Uni. Western Australia.
Lines: 23

Reply to Parent Message