A few weeks ago I discovered TPCircularBuffer, a circular buffer implementation for Darwin operating system implementations, including Mac OS X and iOS. Now, I've implemented circular buffers before, so I though there wasn't much need for yet another circular buffer implementation (let alone one specific to iOS), until I noticed something very interesting in the code.
A trick TPCircularBuffer uses is to map two adjacent memory blocks to the same buffer. The buffer holds the actual data, and the virtual memory manager ensures that both maps contain the exact same data, since effectively both virtual memory blocks remaps to the same memory. This makes things a lot easier than my naive implementations: Rather than dealing with convoluted pointer arithmetics each time the producer or consumer reads or writes a sequence of values that cross the end of the buffer, a simple linear read or write works. In fact, the pointers from that doubly-mapped memory can be safely given to any normal function that accepts a pointer, removing the need to make memory copies before each use of the buffer by an external function.
In fact, this optimization is so common that a previous version of the Wikipedia page for circular buffers had some sample code using common POSIX functions. There's even a 10-year-old VRB - Virtual Ring Buffer library for Linux systems. As for Windows, I've yet to seen some good sample code, but you can do the equivalent with CreateFileMapping and MapViewOfFile.
Both Wikipedia's and VRB's implementations can be misleading, and not very portable though. On Darwin, and I suspect BSD and many other systems, the mapped memory must be fully aligned to the size of a memory page ("allocation granularity" in Windows terms). On POSIX, that means using the value of
sysconf(_SC_PAGESIZE). Since most of the times the page size is a power of 2, that could explain the otherwise strange
buffer->count_bytes = 1UL << order from Wikipedia's sample code.
By the way, I'd like to reiterate how poor the built-in Mac OS X documentation is for POSIX and UNIX-like functions. Though it does warn pretty well about page size alignment and the risks involved with
mmap, the rest of the documentation fails to mention how to set permissions of the memory map. Thankfully, the latest Linux man pages for the same functions are far better documented.
Published on May 23, 2016 at 14:01 EDT
Older post: The Static Blog
Newer post: Good Enough Wireless Audio