FlashMap
FlashMap is a research design that unifies virtual-memory, file-index and flash-address translations for memory-mapped SSD files.
Mapping: Shared leaf page-table pages index a file, while private upper levels enforce process-specific permissions. Custom mprotect regions use private leaf tables. [2] A DRAM-resident data page needs an auxiliary entry remembering its SSD location. [1]
Device contract: A sparse interface assigns a virtual SSD to each mapped file. Metadata retains separate mappings; garbage collection and error correction remain necessary. Reverse mappings and timestamps support rebuilding the shared tables. [1]
Measured scope: The prototype modifies Linux/EXT4 and wraps conventional SSDs. The reported 3.32x speedup concerns connected-component graph processing versus Separate Memory (OnDemand). The 53.2% latency reduction versus Unoptimized Software instead uses DRAM-backed emulation of faster devices, without device-level indirection. It does not measure NAND latency. [1]
Name distinction: FastMap, from ATC 2020, reduces synchronization overhead in Linux's mmap path; it is a different design, not an alias. [3]
Relations
Advantages
- Sharing translation state can leave more DRAM available for application data. [1]
Limitations
- Unified translation does not itself supply atomic application updates; the paper leaves additional transactional mechanisms to future work. [1]
- The evaluated interface requires coordinated OS, filesystem and device changes, not just a normal mmap call on an arbitrary SSD. [1]
Citations
- Huang et al. Unified Address Translation for Memory-Mapped SSDs with FlashMap. ISCA 2015, pp. 580-591, sections 3-5 and 7.
- Huang et al. FlashMap: ISCA 2015 presentation, shared page tables and memory protection (PDF pages 29-44).
- Papagiannis et al. Optimizing Memory-mapped I/O for Fast Storage Devices. USENIX ATC 2020.