11 Jul
2011
11 Jul
'11
10:58 p.m.
On Mon, Jul 11, 2011 at 4:50 PM, Chris Cannam
<cannam(a)all-day-breakfast.com> wrote:
On 11 July 2011 21:32, James Morris
<jwm.art.net(a)gmail.com> wrote:
no, the pragmatic solution is to use memory barriers liberally applied.
I've ended up going back to Fons's
pragmatism. If
non-blocking/lock-free programming is so impossibly difficult,
requiring intimate hardware knowledge of numerous different
architectures then there's only one solution available to people like
me, and that's to code for AMD64/Intel and use the existing ringbuffer
implementations.
Perhaps the pragmatic solution is to _lock_ the shared buffer?