diff options
author | Rich Felker <dalias@aerifal.cx> | 2014-08-15 23:54:52 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2014-08-15 23:54:52 -0400 |
commit | bc09d58c0432a4eca5f6a1e536679a527f971116 (patch) | |
tree | b11245485fda79d368a3bd2d4bb26d9070328a74 /src/thread/pthread_cond_broadcast.c | |
parent | d86af2a0803cace7b0f616f2a696fb3e25e9b628 (diff) | |
download | musl-bc09d58c0432a4eca5f6a1e536679a527f971116.tar.gz musl-bc09d58c0432a4eca5f6a1e536679a527f971116.tar.bz2 musl-bc09d58c0432a4eca5f6a1e536679a527f971116.tar.xz musl-bc09d58c0432a4eca5f6a1e536679a527f971116.zip |
make futex operations use private-futex mode when possible
private-futex uses the virtual address of the futex int directly as
the hash key rather than requiring the kernel to resolve the address
to an underlying backing for the mapping in which it lies. for certain
usage patterns it improves performance significantly.
in many places, the code using futex __wake and __wait operations was
already passing a correct fixed zero or nonzero flag for the priv
argument, so no change was needed at the site of the call, only in the
__wake and __wait functions themselves. in other places, especially
where the process-shared attribute for a synchronization object was
not previously tracked, additional new code is needed. for mutexes,
the only place to store the flag is in the type field, so additional
bit masking logic is needed for accessing the type.
for non-process-shared condition variable broadcasts, the futex
requeue operation is unable to requeue from a private futex to a
process-shared one in the mutex structure, so requeue is simply
disabled in this case by waking all waiters.
for robust mutexes, the kernel always performs a non-private wake when
the owner dies. in order not to introduce a behavioral regression in
non-process-shared robust mutexes (when the owning thread dies), they
are simply forced to be treated as process-shared for now, giving
correct behavior at the expense of performance. this can be fixed by
adding explicit code to pthread_exit to do the right thing for
non-shared robust mutexes in userspace rather than relying on the
kernel to do it, and will be fixed in this way later.
since not all supported kernels have private futex support, the new
code detects EINVAL from the futex syscall and falls back to making
the call without the private flag. no attempt to cache the result is
made; caching it and using the cached value efficiently is somewhat
difficult, and not worth the complexity when the benefits would be
seen only on ancient kernels which have numerous other limitations and
bugs anyway.
Diffstat (limited to 'src/thread/pthread_cond_broadcast.c')
-rw-r--r-- | src/thread/pthread_cond_broadcast.c | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/src/thread/pthread_cond_broadcast.c b/src/thread/pthread_cond_broadcast.c index 0901daf6..18e778f3 100644 --- a/src/thread/pthread_cond_broadcast.c +++ b/src/thread/pthread_cond_broadcast.c @@ -27,13 +27,17 @@ int pthread_cond_broadcast(pthread_cond_t *c) /* Perform the futex requeue, waking one waiter unless we know * that the calling thread holds the mutex. */ + int wake_cnt = !(m->_m_type & 3) + || (m->_m_lock&INT_MAX)!=__pthread_self()->tid; + if (m->_m_type & 128) wake_cnt = INT_MAX; + __syscall(SYS_futex, &c->_c_seq, FUTEX_REQUEUE | 128, + wake_cnt, INT_MAX, &m->_m_lock) != -EINVAL || __syscall(SYS_futex, &c->_c_seq, FUTEX_REQUEUE, - !m->_m_type || (m->_m_lock&INT_MAX)!=__pthread_self()->tid, - INT_MAX, &m->_m_lock); + wake_cnt, INT_MAX, &m->_m_lock); out: a_store(&c->_c_lock, 0); - if (c->_c_lockwait) __wake(&c->_c_lock, 1, 0); + if (c->_c_lockwait) __wake(&c->_c_lock, 1, 1); return 0; } |