
o The processor that creates chares keeps them to itself

o There is an initial and periodic distribution of status information as in the
acwn strategy

o All processors do a periodic check to see if they are low on work.
     If yes (ie load < LowThresh), it sends requests to those of its neighbours
  which have a load greater than SendThresh.

o A processor which receives a request dispatches k chare(s) to the requesting
  processor ,
     where k = (myload>=SendThresh)? ceil((myload - LowThresh) / FanFactor) : 0;
       where FanFactor may be either #defined or f(numNeighbours)
	     SendThresh and LowThresh are again either #defines or varying ints
  If k = 0, a negative acknowledgement is sent.

Should these be #defines or integer variables (varying during execution of
the program) :
 o LowThresh
 o SendThresh
 o FanFactor

Is it necessary to do a status broadcast after all the replies have been 
received - or will the periodic status broadcast be sufficient ? (Note that 
certain amount of complicated (because of versions) bookkeeping is necessary
to verify that all replies have come in).

Is it OK to junk negative acks ?  (NO - one can get back status info that way
- this obviates the need to send out a request to that processor the next time)

When one sends work to another processor, can it just update the local status
info for that processor ?

Is it necessary to have different LowThresh and SendThresh ?



