#mmap #memory-mapped #memory-mapping #memory-map #lock #writers #io


Append-only memory-mapped I/O, resizable, with low lock contention

2 unstable releases

0.2.0 Feb 21, 2024
0.1.0 Jul 29, 2023

#219 in Memory management

MIT license

199 lines


This is a memory mapping crate for unix only.

It derives from the mmap crate, and provides a resizable append-only map with very low lock contention. RwLock<MmapMut> from the mmap crate works, but writers block readers and readers block writers. In our implementation, only writers block writers, or they block everything during a resize. the mmap crate doesn't offer resize functionality.

It uses an interior lock to prevent two different processes from appending at the same time, and a different interior lock to get exclusive access during the resize, which may change the virtual address of the map. The virtual address of the map changing should not matter to callers who access the memory via slices, and there can be no active borrowed slices when the resize happens due to the locking mechanism.