Re: Mutual Exclusion

• Date: Wed, 8 Nov 1995 06:13:18 PST
• From:
  Pieter-Bas IJdens <pbijdens@alchemy.cs.ruu.nl>
• Cc: moo-cows@parc.xerox.com
• Content-Transfer-Encoding: 7bit
• Content-Type: text/plain; charset=US-ASCII
• In-Reply-To: <Pine.LNX.3.91.951109013814.189A-100000@iman.internet.co.nz> from "Ian Macintosh" at Nov 8, 95 04:39:20 am

>Basically, all you need to ensure is that you do not suspend between
>reading the variable, and writing to the variable, and all is well :^)
>
>Regards,
>
>Ian.

I don't think you're right here. I suppose there is some kind of scheduler in
the moo-server, and it just can occur that the two verbs are being
executed at the same time. So maybe at program level everything is ok, but at
server level they might be scheduled wrong, so the problem won't disappear.
The only way of making sure everything is ok is by implementing some kind of
``semaphore'' or ``monitor'' in your moo-code (I think).

robot 1 : 
  1 read(CB,x)
  2 dec(x,100)
  3 write(CB,x)

robot 2:
  4 read(CB,x)
  5 dec(x,200)
  6 write(CB,x)

Might be scheduled like 1 4 2 3 5 6, and the final CB is 100 too high...

Yours,
  
  Pieter-Bas

-- 
                      P.B. IJdens (pbijdens@cs.ruu.nl)
      Department of Computer Science, Utrecht University (the Netherlands)
       WWW: http://huizen.dds.nl/~pbijdens/  (also for my PGP public key)
********************** quod scripsi scripsi (Joh: 19:22) **********************

• Re: Mutual Exclusion
• From: Microwave Systems Admin <root@microwave.com>

• Re: Mutual Exclusion
• From: Ian Macintosh <ian@iman.internet.co.nz>

• Prev: Re: Mutual Exclusion
• Next: Re: Mutual Exclusion
• Index: MOO-cows
• Thread: MOO-cows