SALSA host translation layer
SALSA is a research host translation framework that separates shared storage allocation from workload-specific address mapping across SSDs and SMR disks.
Interface: The MASCOTS 2018 design exposes Linux device-mapper block devices for unmodified applications. It works with commodity drives; it does not require an open-channel SSD or remove an existing drive translation layer. [1]
Mapping: Four-byte entries with 4 KiB pages require 1 GiB per TiB for the flat forward map; 64 KiB pages require 64 MiB. These are map costs, not total RAM. Larger pages can cause read-modify-write for smaller updates. The dual controller adds sparse 4 KiB mappings alongside a full 64 KiB map; if the sparse map is full, read-modify-write remains possible. [1]
Persistence: Mapping updates are logged. Flush forces mapping metadata out; SMR padding and flash metadata updates differ. RAID-5 requires persistent storage for unfinished-stripe parity. [1]
Interpretation: The reported 35.4x MySQL gain compares SALSA with Linux MD on four commodity SATA SSDs, not with a current NVMe array. [1]
Code lineage: The archived uDepot repository contains SALSA code and cites this work for allocation and garbage collection. Its recovery notes require protected device buffers and exclude a general filesystem-backed crash-integrity guarantee; that is an implementation-specific condition, not a universal SALSA promise. [3]
Relations
- related
- Flash translation layer (FTL), uDepot
Citations
- Ioannou, Kourtis and Koltsidas. Elevating Commodity Storage with the SALSA Host Translation Layer. MASCOTS 2018, sections III-C/D, IV-A and V-B.
- IBM uDepot, revision 5b9d9f4c: SALSA allocation/GC lineage and implementation-specific crash-recovery conditions.
- Hesela: exact forward-map arithmetic and explicit exclusions (JSON).
Further reading
Sources & caveats
- Source synthesis, not a hardware benchmark or crash experiment. The linked arithmetic uses map bytes = ceil(capacity bytes / page bytes) * entry bytes; it excludes reverse maps, sparse-map overhead, buffers and allocator state. [4]