mirror of
https://sourceware.org/git/glibc.git
synced 2024-12-04 02:40:06 +00:00
1cdbe57948
Lock elision using TSX is a technique to optimize lock scaling It allows to run locks in parallel using hardware support for a transactional execution mode in 4th generation Intel Core CPUs. See http://www.intel.com/software/tsx for more Information. This patch implements a simple adaptive lock elision algorithm based on RTM. It enables elision for the pthread mutexes and rwlocks. The algorithm keeps track whether a mutex successfully elides or not, and stops eliding for some time when it is not. When the CPU supports RTM the elision path is automatically tried, otherwise any elision is disabled. The adaptation algorithm and its tuning is currently preliminary. The code adds some checks to the lock fast paths. Micro-benchmarks show little to no difference without RTM. This patch implements the low level "lll_" code for lock elision. Followon patches hook this into the pthread implementation Changes with the RTM mutexes: ----------------------------- Lock elision in pthreads is generally compatible with existing programs. There are some obscure exceptions, which are expected to be uncommon. See the manual for more details. - A broken program that unlocks a free lock will crash. There are ways around this with some tradeoffs (more code in hot paths) I'm still undecided on what approach to take here; have to wait for testing reports. - pthread_mutex_destroy of a lock mutex will not return EBUSY but 0. - There's also a similar situation with trylock outside the mutex, "knowing" that the mutex must be held due to some other condition. In this case an assert failure cannot be recovered. This situation is usually an existing bug in the program. - Same applies to the rwlocks. Some of the return values changes (for example there is no EDEADLK for an elided lock, unless it aborts. However when elided it will also never deadlock of course) - Timing changes, so broken programs that make assumptions about specific timing may expose already existing latent problems. Note that these broken programs will break in other situations too (loaded system, new faster hardware, compiler optimizations etc.) - Programs with non recursive mutexes that take them recursively in a thread and which would always deadlock without elision may not always see a deadlock. The deadlock will only happen on an early or delayed abort (which typically happens at some point) This only happens for mutexes not explicitely set to PTHREAD_MUTEX_NORMAL or PTHREAD_MUTEX_ADAPTIVE_NP. PTHREAD_MUTEX_NORMAL mutexes do not elide. The elision default can be set at configure time. This patch implements the basic infrastructure for elision. |
||
|---|---|---|
| .. | ||
| cancellation.S | ||
| clone.S | ||
| compat-timer.h | ||
| fork.c | ||
| Implies | ||
| libc-cancellation.S | ||
| libc-lowlevellock.S | ||
| librt-cancellation.S | ||
| lowlevellock.h | ||
| lowlevellock.S | ||
| lowlevelrobustlock.S | ||
| not-cancel.h | ||
| pt-vfork.S | ||
| pthread_barrier_wait.S | ||
| pthread_cond_broadcast.S | ||
| pthread_cond_signal.S | ||
| pthread_cond_timedwait.S | ||
| pthread_cond_wait.S | ||
| pthread_once.S | ||
| pthread_rwlock_rdlock.S | ||
| pthread_rwlock_timedrdlock.S | ||
| pthread_rwlock_timedwrlock.S | ||
| pthread_rwlock_unlock.S | ||
| pthread_rwlock_wrlock.S | ||
| pthread_setaffinity.c | ||
| pthread_spin_init.c | ||
| pthread_spin_unlock.S | ||
| sem_post.S | ||
| sem_timedwait.S | ||
| sem_trywait.S | ||
| sem_wait.S | ||
| sysdep-cancel.h | ||
| timer_create.c | ||
| timer_delete.c | ||
| timer_getoverr.c | ||
| timer_gettime.c | ||
| timer_settime.c | ||
| Versions | ||
| vfork.S | ||