Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!news.nd.edu!news.cs.indiana.edu!ariel.unm.edu!nmsu!opus!jthomas
From: jthomas@nmsu.edu (James Thomas)
Newsgroups: comp.arch
Subject: Re: Atomic operations (Was Re: Living With Old Baggage)
Message-ID: <1266@opus.NMSU.Edu>
Date: 12 May 91 18:03:47 GMT
References: <336@scorpio.gtephx.UUCP> <12741@pt.cs.cmu.edu>
	<14628@encore.Encore.COM> <1991Apr22.175410.9840@decvax.dec.com>
	<1991May2.201917.15062@dg-rtp.dg.com>
	<1991May6.113149.14531@decvax.dec.com>
Sender: news@NMSU.Edu
Organization: NMSU Computer Science
Lines: 8
In-reply-to: kenton@abyss.zk3.dec.com's message of 6 May 91 11:31:49 GMT

In article <1991May6.113149.14531@decvax.dec.com> kenton@abyss.zk3.dec.com (Jeff Kenton OSG/UEG) writes:

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

Once I've created a lock with Dekker's algorithm, I can do anything :-)

Jim