Brian Behlendorf 058de03caa Clear cv->cv_mutex when not in use ... For debugging purposes the condition varaibles keep track of the mutex used during a wait. The idea is to validate that all callers always use the same mutex. Unfortunately, we have seen cases where the caller reuses the condition variable with a different mutex but in a way which is known to be safe. My reading of the man pages suggests you should not do this and always cv_destroy()/cv_init() a new mutex. However, there is overhead in doing this and it does appear to be allowed under Solaris. To accomidate this behavior cv_wait_common() and __cv_timedwait() have been modified to clear the associated mutex when the last waiter is dropped. This ensures that while the condition variable is in use the incorrect mutex case is detected. It also allows the condition variable to be safely recycled without requiring the overhead of a cv_destroy()/cv_init() as long as it isn't currently in use. Finally, spin lock cv->cv_lock was removed because it is not required. When the condition variable is used properly the caller will always be holding the mutex so the spin lock is redundant. The lock was originally added because I expected to need to protect more than just the cv->cv_mutex. It turns out that was not the case. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>		2010-11-29 11:02:34 -08:00
..
spl	Clear cv->cv_mutex when not in use	2010-11-29 11:02:34 -08:00
splat	Linux 2.6.36 compat, use fops->unlocked_ioctl()	2010-11-10 13:16:12 -08:00
.gitignore	sun-misc-gitignore	2010-01-08 09:37:54 -08:00
Makefile.in	Support custom build directories	2010-09-05 21:49:05 -07:00