✳flâneur — a map of the web's best reading

Zaval.org -> Resources -> Library -> Recursive mutexes by David Butenhof

zaval.org · 1,816 words · saved by 1 readers

Home  Resources  - Procurement Dept.  - Department of HR  - Library  - Training  - Restroom    Recursive mutexes by David Butenhof Original could be found here: Google Groups Newsgroups: comp.programming.threads From: David Butenhof Date: Tue, 17 May 2005 17:19:22 GMT Local: Tues,May 17 2005 1:19 pm Subject: Re: recursive mutexes Uenal Mutlu wrote: > "David Schwartz" wrote >> We really mean what we're saying. Really, really. Recursive mutexes are >>really bad and they really do hide serious bugs. > This is simply not true. Recursive locking is a superset of non-recursive locking. > Everthing possible in non-recursive locking is possible in recursive-locking too, > except deadlocking himself. So then how can recursive-locking be more dangerous > than non-recursive locking? This is simple basic logic. Simple, basic logic. First, implementation of efficient and reliable threaded code revolves around one simple and basic principle: follow y

Zaval.org -> Resources -> Library -> Recursive mutexes by David Butenhof Home Resources - Procurement Dept. - Department of HR - Library - Training - Restroom Recursive mutexes by David Butenhof Original could be found here: Google Groups Newsgroups: comp.programming.threads From: David Butenhof Date: Tue, 17 May 2005 17:19:22 GMT Local: Tues,May 17 2005 1:19 pm Subject: Re: recursive mutexes Uenal Mutlu wrote: > "David Schwartz" wrote >> We really mean what we're saying. Really, really. Recursive mutexes are >>really bad and they really do hide serious bugs. > This is simply not true. Recursi

Explore this link on the map →

saved by

related reading