diff options
| author | Rich Felker <dalias@aerifal.cx> | 2011-08-07 11:14:32 -0400 |
|---|---|---|
| committer | Rich Felker <dalias@aerifal.cx> | 2011-08-07 11:14:32 -0400 |
| commit | b3c08a16c0a085e8de01cdc9de106aaa332d27d5 (patch) | |
| tree | 6b3645eb14be5acf87334a158202d4866efda50b /src/thread/pthread_mutexattr_destroy.c | |
| parent | b2b95a58b4326c8a8aa87fdf6e8b0f6421dbaf99 (diff) | |
| download | musl-b3c08a16c0a085e8de01cdc9de106aaa332d27d5.tar.gz musl-b3c08a16c0a085e8de01cdc9de106aaa332d27d5.tar.bz2 musl-b3c08a16c0a085e8de01cdc9de106aaa332d27d5.tar.xz musl-b3c08a16c0a085e8de01cdc9de106aaa332d27d5.zip | |
simplify unified timed wait code, drop support for newer method
the new absolute-time-based wait kernelside was hard to get right and
basically just code duplication. it could only improve "performance"
when waiting, and even then, the improvement was just slight drop in
cpu usage during a wait.
actually, with vdso clock_gettime, the "old" way will be even faster
than the "new" way if the time has already expired, since it will not
invoke any syscalls. it can determine entirely in userspace that it
needs to return ETIMEDOUT.
Diffstat (limited to 'src/thread/pthread_mutexattr_destroy.c')
0 files changed, 0 insertions, 0 deletions