hi,
Is there any interest in having a lower level ringbuffer type in Boost.Lockfree ?
the ringbuffer will be basically using the same algorithm as the spsc_queue under the hood, but basically separate 'algorithm' from 'storage', right? afaict the spsc_queue can already be used in shared memory, though zero-copy is limited to pushing movable types and consuming via a functor (haven't checked the code for a while, though). mmap for buffer wrapping would be really cool to have, though ... -- a more generic interface would be useful for some use cases, where you can directly access the storage may be useful for some use cases, but when i originally wrote the class, it didn't include it, as i was a bit afraid that the interface might be a bit too fragile. but i don't have a very strong opinion on this. i suppose, you already had a look at the code of the spsc_queue already? cheers, tim