Flash translation layer (FTL)
A flash translation layer maps host logical addresses to physical flash locations and manages flash-specific operations such as reclamation.
An overwrite can change physical placement without changing the host address; obsolete contents can remain until block erasure. Recovery must identify the current copy. [1]
Mapping granularity and in-memory representation are separate choices. A fully resident page table is not required. [4] Recovery-order and snapshot guarantees are separate design contracts; see the linked research concepts.
Relations
- related
- FlashAlloc, vStream, NVMKV, Solid-state drive (SSD), eMMC (embedded MultiMediaCard), UFS (Universal Flash Storage), NAND flash, Garbage collection (flash), Wear leveling, Zoned namespaces (ZNS), Host memory buffer (HMB), SSD DRAM cache, SSD mapping cache, FTL translation page, Prefix-preserving crash consistency, Snapshot-consistent flash translation layer, Page-level mapping (FTL), Block-level mapping (FTL), Global Translation Directory (DFTL), Nameless write, Block Padding LRU (BPLRU), Reverse mapping (FTL), Content-aware FTL, TPFTL, Page-differential logging, IceClave, Multi-stream SSD, SimpleSSD, LightNVM, Software-defined flash (SDF), pblk, FlashMap, SALSA host translation layer, WARM, NAND retention relaxation
Citations
- Agrawal et al. Design Tradeoffs for SSD Performance. USENIX ATC 2008, pp. 57-70, sections 3.1, 3.4 and 4.
- Gupta, Kim and Urgaonkar. DFTL: Demand-based Selective Caching of Page-level Address Mappings. ASPLOS 2009, sections 2-3.