Byte-addressable storage
Byte-addressable storage exposes individual byte locations rather than only block-sized addresses, without by itself specifying atomicity or durability.
For memory-like storage, Linux DAX can expose file contents through a direct userspace mapping and avoid a page-cache copy. [1] Addressability is distinct from persistence: PMDK separates page, cache-line and byte persistence granularity according to the protected domain. [2] Even a persistence function is not transactional, and cache eviction can make stores durable before software explicitly persists them. A byte-addressed interface therefore does not promise an atomic multi-byte update. [3] Linux's Block Translation Table (BTT) provides sector-update atomicity through a stacked block device with remapping metadata, rather than deriving that guarantee from byte addressability alone. [4]
Relations
- related
- Persistent memory, Storage-class memory (SCM), NVDIMM-N, Intel Optane, 3D XPoint, CXL memory expansion, Block storage, Direct Access, Persistence domain, Persistence ordering
Advantages
- Suitable DAX mappings avoid the redundant page-cache copy of memory-like backing storage. [1]
Limitations
Citations
- Linux kernel documentation. Direct Access for files: motivation and S_DAX state.
- PMDK 1.13.1. libpmem2(7), GRANULARITY (pinned source documentation).
- PMDK 1.13.1. pmem2_get_persist_fn(3): early persistence and non-transactional semantics.
- Linux kernel documentation. BTT - Block Translation Table, introduction and theory of operation.