|
|
Message-Id: <cover.1498228733.git.Jens.Gustedt@inria.fr>
Date: Fri, 23 Jun 2017 16:38:53 +0200
From: Jens Gustedt <Jens.Gustedt@...ia.fr>
To: musl@...ts.openwall.com
Subject: [PATCH 0/8] the new __lock and follow up patches
Here comes a
Jens Gustedt (8):
(V2) a new lock algorithm with lock value and CS counts in the same
atomic int
consistently use the LOCK an UNLOCK macros
revise the definition of multiple basic locks in the code
determine the existence of private futexes at the first thread
creation
separate the fast parts of __lock and __unlock into a .h file that may
be used by other TU
use the new lock algorithm for malloc
implement __unlock_requeue
implement the local lock for conditions with __lock & Co
src/dirent/__dirent.h | 2 +-
src/exit/at_quick_exit.c | 2 +-
src/exit/atexit.c | 2 +-
src/internal/__lock.h | 30 +++++++++++++++++++++
src/internal/libc.h | 3 +++
src/internal/pthread_impl.h | 16 ++++++++----
src/locale/dcngettext.c | 2 +-
src/locale/locale_map.c | 2 +-
src/locale/setlocale.c | 2 +-
src/malloc/lite_malloc.c | 2 +-
src/malloc/malloc.c | 38 ++++++++++-----------------
src/misc/syslog.c | 2 +-
src/prng/random.c | 2 +-
src/stdio/ofl.c | 2 +-
src/thread/__lock.c | 52 ++++++++++++++++++++++++++++++++-----
src/thread/__timedwait.c | 3 +--
src/thread/__wait.c | 5 ++--
src/thread/pthread_atfork.c | 2 +-
src/thread/pthread_barrier_wait.c | 3 +--
src/thread/pthread_cond_timedwait.c | 49 +++++++++++-----------------------
src/thread/pthread_create.c | 16 +++++++++---
src/thread/pthread_detach.c | 4 +--
src/thread/pthread_getschedparam.c | 4 +--
src/thread/pthread_kill.c | 4 +--
src/thread/pthread_setschedparam.c | 4 +--
src/thread/pthread_setschedprio.c | 4 +--
src/thread/sem_open.c | 2 +-
src/thread/synccall.c | 2 +-
src/time/__tz.c | 2 +-
29 files changed, 157 insertions(+), 106 deletions(-)
create mode 100644 src/internal/__lock.h
base-commit: 8fe1f2d79b275b7f7fb0d41c99e379357df63cd9
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.