John Polstra e6f0183bff Remove the nanosleep calls from the spin loops in the locking code. ... They provided little benefit (if any) and they caused some problems in OpenOffice, at least in post-KSE -current and perhaps in other environments too. The nanosleep calls prevented the profiling timer from advancing during the spinloops, thereby preventing the thread scheduler from ever pre-empting the spinning thread. Alexander Kabaev diagnosed this problem, Martin Blapp helped with testing, and Matt Dillon provided some helpful suggestions. This is a short-term fix for a larger problem. The use of spinlocking isn't guaranteed to work in all cases. For example, if the spinning thread has higher priority than all other threads, it may never be pre-empted, and the thread holding the lock may never progress far enough to release the lock. On the other hand, spinlocking is the only locking that can work with an arbitrary unknown threads package. I have some ideas for a much better fix in the longer term. It would eliminate all locking inside the dynamic linker by making it safe for symbol lookups and lazy binding to proceed in parallel with a call to dlopen or dlclose. This means that the only mutual exclusion needed would be to prevent multiple simultaneous calls to dlopen and/or dlclose. That mutual exclusion could be put into the native pthreads library. Applications using foreign threads packages would have to make their own arrangements to ensure that they did not have multiple threads in dlopen and/or dlclose -- a reasonable requirement in my opinion. MFC after: 3 days		2002-07-06 20:25:56 +00:00
..
lockdflt.c	Remove the nanosleep calls from the spin loops in the locking code.	2002-07-06 20:25:56 +00:00
Makefile.inc
reloc.c	The last bits of the alloca -> mmap fix. IA64 and SPARC64 (current only).	2002-06-22 18:36:21 +00:00
rtld_machdep.h	Update rtld for the "new" ia64 ABI. In the old toolchain, the	2001-10-29 10:10:10 +00:00
rtld_start.S