Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!helios.ee.lbl.gov!ucsd!hub!tomato!panzer
From: panzer@tomato.ucsb.edu (Panzer, John Robert)
Newsgroups: comp.sys.amiga.tech
Subject: Question about ReleaseSemaphore()
Keywords: ReleaseSemaphore
Message-ID: <3156@hub.UUCP>
Date: 29 Nov 89 05:10:41 GMT
Sender: news@hub.UUCP
Reply-To: panzer@cornu.ucsb.edu (Panzer)
Organization: University of California, Santa Barbara
Lines: 18


I'm trying to implement a low-overhead shared (read) lock using
signal semaphores, and I've come up with a way that will work
if several tasks can effectively share ownership of a semaphore.
So, my question is: 

What happens if a task ReleaseSemaphore()'s a semaphore which another
task had previously ObtainSemaphore()'d?  The semaphore structure
has a field for the owner of the semaphore; would changing this field 
prior to the release be necessary or desirable? 

Thanks in advance,


==========================================================================
| John Panzer           | University of California, Santa Barbara        |
| panzer@cornu.ucsb.edu |        SCHOOL OF COMPUTER VIOLENCE             |  
==========================================================================