mirror of
https://github.com/jart/cosmopolitan.git
synced 2025-03-04 07:58:21 +00:00
2f48a02b44
Recursive mutexes now go as fast as normal mutexes. The tradeoff is they are no longer safe to use in signal handlers. However you can still have signal safe mutexes if you set your mutex to both recursive and pshared. You can also make functions that use recursive mutexes signal safe using sigprocmask to ensure recursion doesn't happen due to any signal handler The impact of this change is that, on Windows, many functions which edit the file descriptor table rely on recursive mutexes, e.g. open(). If you develop your app so it uses pread() and pwrite() then your app should go very fast when performing a heavily multithreaded and contended workload For example, when scaling to 40+ cores, *NSYNC mutexes can go as much as 1000x faster (in CPU time) than the naive recursive lock implementation. Now recursive will use *NSYNC under the hood when it's possible to do so |
||
|---|---|---|
| .. | ||
| atm_log.c | ||
| atm_log.h | ||
| BUILD.mk | ||
| closure.c | ||
| closure.h | ||
| counter_test.c | ||
| cv2_test.c | ||
| cv3_test.c | ||
| cv_mu_timeout_stress2_test.c | ||
| cv_mu_timeout_stress3_test.c | ||
| cv_mu_timeout_stress_test.c | ||
| cv_mu_timeout_stress_test.inc | ||
| cv_test.c | ||
| cv_test.inc | ||
| cv_wait_example_test.c | ||
| dll_test.c | ||
| mu2_test.c | ||
| mu3_test.c | ||
| mu_starvation_test.c | ||
| mu_test.c | ||
| mu_test.inc | ||
| mu_wait2_test.c | ||
| mu_wait3_test.c | ||
| mu_wait_example_test.c | ||
| mu_wait_test.c | ||
| mu_wait_test.inc | ||
| note_test.c | ||
| once_test.c | ||
| pingpong_test.c | ||
| smprintf.c | ||
| smprintf.h | ||
| start_thread.c | ||
| testing.c | ||
| testing.h | ||
| time_extra.c | ||
| time_extra.h | ||
| wait_test.c | ||