Searched hist:212077 (Results 1 - 6 of 6) sorted by relevance
| /freebsd-10.0-release/lib/libthr/thread/ | ||
| H A D | thr_fork.c | diff 212077 Wed Sep 01 01:18:00 MDT 2010 davidxu Change atfork lock from mutex to rwlock, also make mutexes used by malloc() module private type, when private type mutex is locked/unlocked, thread critical region is entered or leaved. These changes makes fork() async-signal safe which required by POSIX. Note that user's atfork handler still needs to be async-signal safe, but it is not problem of libthr, it is user's responsiblity. |
| H A D | thr_umtx.c | diff 212077 Wed Sep 01 01:18:00 MDT 2010 davidxu Change atfork lock from mutex to rwlock, also make mutexes used by malloc() module private type, when private type mutex is locked/unlocked, thread critical region is entered or leaved. These changes makes fork() async-signal safe which required by POSIX. Note that user's atfork handler still needs to be async-signal safe, but it is not problem of libthr, it is user's responsiblity. |
| H A D | thr_umtx.h | diff 212077 Wed Sep 01 01:18:00 MDT 2010 davidxu Change atfork lock from mutex to rwlock, also make mutexes used by malloc() module private type, when private type mutex is locked/unlocked, thread critical region is entered or leaved. These changes makes fork() async-signal safe which required by POSIX. Note that user's atfork handler still needs to be async-signal safe, but it is not problem of libthr, it is user's responsiblity. |
| H A D | thr_init.c | diff 212077 Wed Sep 01 01:18:00 MDT 2010 davidxu Change atfork lock from mutex to rwlock, also make mutexes used by malloc() module private type, when private type mutex is locked/unlocked, thread critical region is entered or leaved. These changes makes fork() async-signal safe which required by POSIX. Note that user's atfork handler still needs to be async-signal safe, but it is not problem of libthr, it is user's responsiblity. |
| H A D | thr_mutex.c | diff 212077 Wed Sep 01 01:18:00 MDT 2010 davidxu Change atfork lock from mutex to rwlock, also make mutexes used by malloc() module private type, when private type mutex is locked/unlocked, thread critical region is entered or leaved. These changes makes fork() async-signal safe which required by POSIX. Note that user's atfork handler still needs to be async-signal safe, but it is not problem of libthr, it is user's responsiblity. |
| H A D | thr_private.h | diff 212077 Wed Sep 01 01:18:00 MDT 2010 davidxu Change atfork lock from mutex to rwlock, also make mutexes used by malloc() module private type, when private type mutex is locked/unlocked, thread critical region is entered or leaved. These changes makes fork() async-signal safe which required by POSIX. Note that user's atfork handler still needs to be async-signal safe, but it is not problem of libthr, it is user's responsiblity. |
Completed in 103 milliseconds