|author||Rich Felker <email@example.com>||2011-09-28 18:57:18 -0400|
|committer||Rich Felker <firstname.lastname@example.org>||2011-09-28 18:57:18 -0400|
improve pshared barriers
eliminate the sequence number field and instead use the counter as the futex because of the way the lock is held, sequence numbers are completely useless, and this frees up a field in the barrier structure to be used as a waiter count for the count futex, which lets us avoid some syscalls in the best case. as of now, self-synchronized destruction and unmapping should be fully safe. before any thread can return from the barrier, all threads in the barrier have obtained the vm lock, and each holds a shared lock on the barrier. the barrier memory is not inspected after the shared lock count reaches 0, nor after the vm lock is released.
Diffstat (limited to 'src/linux')
0 files changed, 0 insertions, 0 deletions