Peter Horton wrote: > I've seen code written for X86 use MAP_FIXED to create self wrapping > ring buffers. Surely it's better to fail the mmap() on other archs > rather than for the code to fail in unexpected ways? Such code should test the buffers or just not create ring buffers on architectures it doesn't know about. (You can usually simulate them by copying data). On some architectures there is _no_ alignment which works, and even on x86 aligning aliases to 32k results in faster memory accesses on some chips (AMD ones). Also, sometimes a self wrapping ring buffer can work even when the separation isn't coherent, provided the code using it forces cache line flushes at the appropriate points. -- Jamie
