[M3commit] CVS Update: cm3

[Jay]

We should probably add a new type Thread.RecursiveExclusiveLock? And then just use that here?
The basic Win32 critical section is such a thing precisely. Not that it is all that great. But it is widely used.
Vista adds the "SRWLock" which is a small read/write lock and maybe reduced recursive functionality.
It is indeed small, just the size of a pointer, whereas a critical section is fairly large.
 
 - Jay



Date: Thu, 14 Aug 2008 20:11:19 -0400From: rcoleburn at scires.comTo: jay.krell at cornell.edu; jkrell at elego.de; m3commit at elegosoft.comSubject: Re: [M3commit] CVS Update: cm3

Jay:
 
There is the abstraction of multiple concurrent "readers" but only one "writer".  I actually have such a module that I use sometimes in my programs.  The idea is one of acquiring/releasing read locks and write locks.  The difficulty here is in preventing starvation and usually requires adherence to some rules (again rigor).  By starvation I mean that writers must wait for all readers to finish before they get access, so if there is always at least one reader, the writer will "starve" and never gain access.
 
As for recursive locks, again that is usually indicative of a design flaw.  I did once implement a system that permitted the same thread to acquire a lock multiple times, provided that it eventually released the lock the same number of times that it acquired it.  In other words, after the first lock, subsequent locks by the same thread just increment a counter.  Then, unlocks decrement the counter until it is zero with the final unlock actually releasing the mutex.
 
In the code you modified, you could implement such a scheme to handle the recursive locks, provided that at some point the thread releases for each lock.  The Thread interface has the ability to note the current thread (i.e., Thread.Self()).  So you could make a stack of locks by same thread.  Other threads would have to block until the first thread's lock stack was empty.
 
For example:
 
ACQUIRE:  If resource available, lock resource mutex and put current thread on granted stack.  Otherwise, if current thread already on granted stack, push it on stack again and let it proceed.  Otherwise (this is a new thread wanting access), so push this thread onto a waiting stack and wait.
 
RELEASE:  Pop granted stack and check to ensure the popped stack entry represents the current thread.  If not, must crash due to a programming error.  If granted stack is now empty, check to see if the waiting stack is empty.  If the waiting stack is empty, release the resource mutex.  Otherwise (there is at least one thread waiting), pop waiting stack and push onto granted stack.  Repeat pop/push for each occurrence of current thread at top of waiting stack.  Allow waiting thread to proceed.
 
I can check into providing my read-write locks modules if needed.
 
Regards,
Randy>>> Jay <jay.krell at cornell.edu> 8/14/2008 6:08 PM >>>Maybe we should have another lock type that allows recursive acquires?To be used sparingly, but used here?I know that is often frowned upon -- the need for it implies a design flaw -- butmaybe it is ok sometimes?I don't understand when/why recursive locks are ok or not.- Jay________________________________From: jay.krell at cornell.eduTo: rcoleburn at scires.com; jkrell at elego.de; m3commit at elegosoft.comDate: Thu, 14 Aug 2008 22:05:13 +0000Subject: Re: [M3commit] CVS Update: cm3How about this comment in the code:(*-------------------------------------------------- raw seething windows ---*)(* NOTE: The helper procedures called by WindowProc lock VBT.mu when calling   various Trestle procedures.  They do not hold locks while calling Win32   because it knows nothing about Modula-3 locks and it can, on a whim, call   WindowProc to do something.  The only reason this scheme might work is   because we have a single Modula-3 thread that's pulling on the Win32   message queue and calling WindowProc.   Similarly, we don't bother locking around updates to Child records.   They are updated by the single Modula-3/WindowProc thread.*)?I also need to check if any state has been modified, or cached in locals, withthe locks held that are being released.-Jay________________________________Date: Thu, 14 Aug 2008 11:13:25 -0400From: rcoleburn at scires.comTo: jkrell at elego.de; m3commit at elegosoft.comSubject: Re: [M3commit] CVS Update: cm3Jay:I haven't studied this code in depth, but on the surface I doubt your change is "correct".I think the more telling problem is that if you look at the body of WinTrestle.Release, it is empty, save for a comment that it is not yet implemented.  So, it would seem that if WinTrestle.Acquire is called more than once, you will crash because the locks have not been released.Further, I don't think it would make sense to release the locks before calling out to Windows, and then reacquire them upon return.  The locks are known to Modula-3 and not Windows.  Releasing them will allow other competing threads to acquire them while you are in the Windows subsystem and would seem to violate whatever protections were in place per holding the locks.  Upon return from Windows, the thread will be back in competition with others to reacquire the locks it gave up and upon success, there is no guarantee that the other threads didn't disturb the state the original thread depended upon.I would suggest reverting these changes and looking to implement the Release procedure.Regards,Randy>>> Jay Krell  8/14/2008 4:26 PM>>>CVSROOT:/usr/cvsChanges by:jkrell at birch.08/08/14 16:26:59Modified files:cm3/m3-ui/ui/src/winvbt/: WinTrestle.m3Log message:release locks when calling out to Win32 to prevent recursive lock acquisition. correct?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20080815/267507ca/attachment-0002.html>