|author||Rich Felker <firstname.lastname@example.org>||2012-04-24 16:32:23 -0400|
|committer||Rich Felker <email@example.com>||2012-04-24 16:32:23 -0400|
ditch the priority inheritance locks; use malloc's version of lock
i did some testing trying to switch malloc to use the new internal lock with priority inheritance, and my malloc contention test got 20-100 times slower. if priority inheritance futexes are this slow, it's simply too high a price to pay for avoiding priority inversion. maybe we can consider them somewhere down the road once the kernel folks get their act together on this (and perferably don't link it to glibc's inefficient lock API)... as such, i've switch __lock to use malloc's implementation of lightweight locks, and updated all the users of the code to use an array with a waiter count for their locks. this should give optimal performance in the vast majority of cases, and it's simple. malloc is still using its own internal copy of the lock code because it seems to yield measurably better performance with -O3 when it's inlined (20% or more difference in the contention stress test).
Diffstat (limited to 'dist/config.mak')
0 files changed, 0 insertions, 0 deletions