| |||||||||||||
what's needed is a application barrier() callwhat's needed is a application barrier() callPosted Sep 10, 2009 11:18 UTC (Thu) by nix (subscriber, #2304)In reply to: what's needed is a application barrier() call by ras Parent article: POSIX v. reality: A position on O_PONIES
He then worked for years to get a standard set of functions that solved the problem to be added to the C standard library.Obviously I missed something, but userspace RCU isn't in glibc and certainly isn't in POSIX.
(Log in to post comments)
what's needed is a application barrier() call Posted Sep 10, 2009 12:19 UTC (Thu) by ras (subscriber, #33059) [Link]
> Obviously I missed something, but userspace RCU isn't in glibc
> and certainly isn't in POSIX.
Paul describes his efforts so far here: http://www.rdrop.com/users/paulmck/scalability/paper/CPP-...
what's needed is a application barrier() call Posted Sep 10, 2009 13:37 UTC (Thu) by nix (subscriber, #2304) [Link]
Ah, thanks, great stuff. I didn't realise the 'threads cannot be implemented in a library' standardization fix had got as far as this. I'd encountered bits of this (quick_exit()), but not realised why they were useful.
(And Paul's slides are the best explanation of the problem I've ever seen. Slide 26 is particularly good ;} )
|
|||||||||||||