what's needed is a application barrier() call
what's needed is a application barrier() call
Posted Sep 10, 2009 1:43 UTC (Thu) by ras (subscriber, #33059)In reply to: what's needed is a application barrier() call by vaurora
Parent article: POSIX v. reality: A position on O_PONIES
Maybe write barriers are just the interface we need, maybe not. What we need is a Paul McKenney to do for this problem what Paul did for a very similar problem in multi CPU memory architectures. He wrote the RCU stuff and in the process became intimately familiar for the problem and all possible solutions. He then worked for years to get a standard set of functions that solved the problem to be added to the C standard library. Where is your white knight in shining armour when you need them? Who knows, maybe our knight will be female for a change.
One thing hasn't changed though, and that is the ability of the female of our special to create work. Now I feel compelled to learn about Featherstich.
Posted Sep 10, 2009 11:18 UTC (Thu)
by nix (subscriber, #2304)
[Link] (2 responses)
Posted Sep 10, 2009 12:19 UTC (Thu)
by ras (subscriber, #33059)
[Link] (1 responses)
Paul describes his efforts so far here: http://www.rdrop.com/users/paulmck/scalability/paper/CPP-...
Posted Sep 10, 2009 13:37 UTC (Thu)
by nix (subscriber, #2304)
[Link]
(And Paul's slides are the best explanation of the problem I've ever seen. Slide 26 is particularly good ;} )
Posted Sep 10, 2009 11:19 UTC (Thu)
by nix (subscriber, #2304)
[Link]
what's needed is a application barrier() call
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.
what's needed is a application barrier() call
> and certainly isn't in POSIX.
what's needed is a application barrier() call
what's needed is a application barrier() call