🚀 go-pugleaf

Jonathan Benedicto wrote:
> "Dennis Jones" <nospam@nospam.com> wrote in message 
> news:429354a6@newsgroups.borland.com...
> 
>>A critical section is the most efficient (in terms of performance) 
>>kernel
>>mode synchronization primitive.  If you are looking for performance, 
>>a
>>critical section is the way to go.  Though it might seem slower 
>>than, say, a
>>boolean lock, it is safe, while a boolean lock is not.
>>
>>On the other hand, depending on what the other threads are doing, it 
>>might
>>be faster to lock the whole vector, do your search, and then unlock 
>>(as
>>opposed to locking each element individually).
> 
> Thank you for this input. I'm going to try a critical section, and see 
> how it works out.

Jonathan :  To reduce the size and amount of time spent within the 
Critical Section, you might consider using a Critical Section to manage 
only the 'Boolean lock' access then you can be certain of the 'lock' 
status ie.  <CS begin>test or transition boolean/<CS end>.  It also 
means only the entry you're working on is restricted (by the CS) rather 
than the entire vector.
---------->  signature = 6 lines follows <--------------
Neil Duffee, Joe SysProg, U d'Ottawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585                 fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca     http:/ /aix1.uottawa.ca/ ~nduffee
"How *do* you plan for something like that?" Guardian Bob, Reboot
"For every action, there is an equal and opposite criticism."
"Systems Programming: Guilty, until proven innocent" John Norgauer 2004