device-dax · shipping · also devdax, device-dax

Device DAX

Device DAX is a Linux character-device interface for mapping a memory region directly into an application without filesystem page-cache buffering.

Related Observatory article: Read on hesela.com

Applications map /dev/daxN.Y with mmap() and manage allocations within that region. This differs from filesystem DAX, which exposes file data, and from dax_kmem, which hands capacity to Linux memory hotplug. [1] [3]

Hotplug registration is not the same as online System RAM. Blocks must be online before the page allocator can use them; the selected zone controls eligible allocations. A Device DAX device can have a NUMA association, so a node identifier alone does not prove that its capacity is online. [4] [5]

CXL regions reserved by firmware or provisioned after boot can use Device DAX, while firmware can also expose CXL capacity as System RAM during boot. The interface is not restricted to persistent memory: the CXL device may supply volatile capacity. [2] [6]

Relations

related
CXL memory expansion, Direct Access, Byte-addressable storage, Persistent memory

Advantages

  • Applications can explicitly manage a mapped memory region instead of receiving that capacity through the kernel page allocator. [1]

Limitations

  • daxctl v80 documents mode reconfiguration as destructive: existing contents are lost. It is not a data-preserving switch between devdax and system-ram. [5]
  • Mapping a volatile CXL region does not make its contents persistent across power loss. [6]

Citations

  1. Linux 6.17: DAX Driver Operation, direct mappings and kmem conversion. (accessed 2026-11-11)
  2. Linux 6.17: Device DAX, CXL and KMEM configuration. (accessed 2026-11-11)
  3. Linux 6.17: Direct Access for files, page-cache bypass and file mappings. (accessed 2026-11-11)
  4. Linux 6.17: Memory Hotplug, online states and allocation zones. (accessed 2026-11-11)
  5. daxctl v80: reconfigure-device, destructive conversion and separate onlining. (accessed 2026-11-11)
  6. Linux 6.17: CXL devices and protocols, volatile and persistent capacity. (accessed 2026-11-11)
Sources & caveats
  • Source-backed description scoped to Linux 6.17 and daxctl v80; no device experiment or current-platform compatibility claim.
  • The NUMA/allocator distinction is inferred from the documented devdax target_node example and separate memory-block onlining state.
  • The existing dax identifier retains its filesystem-DAX meaning; device-dax identifies the character-device interface, not a renamed copy.

JSON: /data/terms/device-dax.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Device DAX. Hesela. 2026-11-11. https://hesela.dev/terms/device-dax/