Is there a good , current description of how & why the various mutexe's
& conditon variables are used for somewhere?? I see what they are doing
in the code, but would like to get the big picture of why they are used
in one place (and not another type)..
> I'm not against the concept of multiple pools, but I'm not really
> for it either. The various mutexes are already far too complex
> for their own good... look at SX locks, for example. The
> struct sx is about 8 times as big as it needs to be to implement
> reasonable functionality. I would scrap the upgrade and
> downgrade API and I would scrap the condition variables
> and go with a simple shared/exclusive counter.
> Matthew Dillon
> <[EMAIL PROTECTED]>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message