process-shared barrier support, based on discussion with bdonlan
authorRich Felker <dalias@aerifal.cx>
Tue, 27 Sep 2011 17:50:29 +0000 (13:50 -0400)
committerRich Felker <dalias@aerifal.cx>
Tue, 27 Sep 2011 17:50:29 +0000 (13:50 -0400)
commit60164570111873175111cf8a5b973375e492eee9
tree1557931c4e0bacd2be217965be08031d5e3a4e51
parent3f39c9b3130cd6c142d358159879b799370a6663
process-shared barrier support, based on discussion with bdonlan

this implementation is rather heavy-weight, but it's the first
solution i've found that's actually correct. all waiters actually wait
twice at the barrier so that they can synchronize exit, and they hold
a "vm lock" that prevents changes to virtual memory mappings (and
blocks pthread_barrier_destroy) until all waiters are finished
inspecting the barrier.

thus, it is safe for any thread to destroy and/or unmap the barrier's
memory as soon as pthread_barrier_wait returns, without further
synchronization.
src/internal/pthread_impl.h
src/mman/mmap.c
src/mman/munmap.c
src/thread/pthread_barrier_destroy.c
src/thread/pthread_barrier_init.c
src/thread/pthread_barrier_wait.c
src/thread/pthread_barrierattr_setpshared.c