Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!cs395t54
From: cs395t54@cs.utexas.edu (Pow Hwee Tan)
Newsgroups: comp.sys.transputer
Subject: Re: transputer scheduler
Keywords: priority
Message-ID: <372@megalon.cs.utexas.edu>
Date: 1 Apr 89 17:37:49 GMT
References: <5339@latcs1.oz>
Organization: U. Texas CS Dept., Austin, Texas
Lines: 21


About whether running a segment of code like

  PAR
    p1
    p2

will run sequentially or parallel on a SINGLE transputer, my experience
tells me that the transputer did do a time slice scheduling. This
is because if the above code were to run on a single transputer then
it will run slower than a sequential one, ie:

  SEQ
    p1
    p2

The slower performance is due to task switching.

pow-hwee tan
--
tph@minnie.cc.utexas.edu