Date: Fri, 7 Jul 2000 21:10:38 -0700 (PDT) From: John Polstra <jdp@FreeBSD.org> To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/libexec/rtld-elf rtld.c rtld.h lockdflt.c src/libexec/rtld-elf/alpha lockdflt.c rtld_machdep.h rtld_start.S src/libexec/rtld-elf/i386 lockdflt.c rtld_machdep.h Message-ID: <200007080410.VAA94282@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
jdp 2000/07/07 21:10:38 PDT
Modified files:
libexec/rtld-elf rtld.c rtld.h
libexec/rtld-elf/alpha lockdflt.c rtld_machdep.h rtld_start.S
libexec/rtld-elf/i386 lockdflt.c rtld_machdep.h
Removed files:
libexec/rtld-elf lockdflt.c
Log:
Solve the dynamic linker's problems with multithreaded programs once
and for all (I hope). Packages such as wine, JDK, and linuxthreads
should no longer have any problems with re-entering the dynamic
linker.
This commit replaces the locking used in the dynamic linker with a
new spinlock-based reader/writer lock implementation. Brian
Fundakowski Feldman <green> argued for this from the very beginning,
but it took me a long time to come around to his point of view.
Spinlocks are the only kinds of locks that work with all thread
packages. But on uniprocessor systems they can be inefficient,
because while a contender for the lock is spinning the holder of the
lock cannot make any progress toward releasing it. To alleviate
this disadvantage I have borrowed a trick from Sleepycat's Berkeley
DB implementation. When spinning for a lock, the requester does a
nanosleep() call for 1 usec. each time around the loop. This will
generally yield the CPU to other threads, allowing the lock holder
to finish its business and release the lock. I chose 1 usec. as the
minimum sleep which would with reasonable certainty not be rounded
down to 0.
The formerly machine-independent file "lockdflt.c" has been moved
into the architecture-specific subdirectories by repository copy.
It now contains the machine-dependent spinlocking code. For the
spinlocks I used the very nifty "simple, non-scalable reader-preference
lock" which I found at
<http://www.cs.rochester.edu/u/scott/synchronization/pseudocode/rw.html>;
on all CPUs except the 80386 (the specific CPU model, not the
architecture). The 80386 CPU doesn't support the necessary "cmpxchg"
instruction, so on that CPU a simple exclusive test-and-set lock
is used instead. 80386 CPUs are detected at initialization time by
trying to execute "cmpxchg" and catching the resulting SIGILL
signal.
To reduce contention for the locks, I have revamped a couple of
key data structures, permitting all common operations to be done
under non-exclusive (reader) locking. The only operations that
require exclusive locking now are the rare intrusive operations
such as dlopen() and dlclose().
The dllockinit() interface is now deprecated. It still exists,
but only as a do-nothing stub. I plan to remove it as soon as is
reasonably possible. (From the very beginning it was clearly
labeled as experimental and subject to change.) As far as I know,
only the linuxthreads port uses dllockinit(). This interface turned
out to have several problems. As one example, when the dynamic
linker called a client-supplied locking function, that function
sometimes needed lazy binding, causing re-entry into the dynamic
linker and a big looping mess. And in any case, it turned out to be
too burdensome to require threads packages to register themselves
with the dynamic linker.
Revision Changes Path
1.46 +135 -115 src/libexec/rtld-elf/rtld.c
1.18 +19 -6 src/libexec/rtld-elf/rtld.h
1.5 +113 -44 src/libexec/rtld-elf/alpha/lockdflt.c
1.4 +8 -2 src/libexec/rtld-elf/alpha/rtld_machdep.h
1.4 +51 -4 src/libexec/rtld-elf/alpha/rtld_start.S
1.5 +207 -43 src/libexec/rtld-elf/i386/lockdflt.c
1.4 +23 -2 src/libexec/rtld-elf/i386/rtld_machdep.h
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007080410.VAA94282>