🚀 go-pugleaf

In article <1991May2.201917.15062@dg-rtp.dg.com>,
hamilton@siberia.rtp.dg.com (Eric Hamilton) writes:
|> In article <1991Apr22.175410.9840@decvax.dec.com>,
kenton@abyss.zk3.dec.com (Jeff Kenton OSG/UEG) writes:
|> |> 
|> |> The 88K has xmem, not test and set, which is guaranteed to be an atomic
|> |> operation (the bus is locked between the read and write cycles).  This
|> |> can be used to create locks or compare and swap without disabling
itnerrupts.
|> |> 
|> Now I'm curious.  How does one fabricate compare-and-swap out of xmem
|> without disabling interrupts?  Xmem has essentially the same restriction as
|> test-and-set, which is that the stored value must be a constant
independent of
|> the loaded value.
|> 

Once you've created a lock (with xmem) you can do almost anything within the
locked region of code without disabling interrupts.

-----------------------------------------------------------------------------
==	jeff kenton		Consulting at kenton@decvax.dec.com        ==
==	(617) 894-4508			(603) 881-0011			   ==
-----------------------------------------------------------------------------