{
  "slug": "device-dax",
  "term": "Device DAX",
  "aliases": [
    "devdax",
    "device-dax"
  ],
  "definition": "Device DAX is a Linux character-device interface for mapping a memory region directly into an application without filesystem page-cache buffering.",
  "note": "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. [dax-617] [fsdax-617]\n\nHotplug 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. [hotplug-617] [daxctl-80]\n\nCXL 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. [kconfig-617] [types-617]",
  "status": "shipping",
  "advantages": [
    {
      "text": "Applications can explicitly manage a mapped memory region instead of receiving that capacity through the kernel page allocator.",
      "citationIds": [
        "dax-617"
      ]
    }
  ],
  "limitations": [
    {
      "text": "daxctl v80 documents mode reconfiguration as destructive: existing contents are lost. It is not a data-preserving switch between devdax and system-ram.",
      "citationIds": [
        "daxctl-80"
      ]
    },
    {
      "text": "Mapping a volatile CXL region does not make its contents persistent across power loss.",
      "citationIds": [
        "types-617"
      ]
    }
  ],
  "related": [
    "cxl-memory",
    "dax",
    "byte-addressable-storage",
    "persistent-memory"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "citations": [
    {
      "id": "dax-617",
      "title": "Linux 6.17: DAX Driver Operation, direct mappings and kmem conversion.",
      "url": "https://docs.kernel.org/6.17/driver-api/cxl/linux/dax-driver.html",
      "accessed": "2026-11-11"
    },
    {
      "id": "kconfig-617",
      "title": "Linux 6.17: Device DAX, CXL and KMEM configuration.",
      "url": "https://github.com/torvalds/linux/blob/v6.17/drivers/dax/Kconfig",
      "accessed": "2026-11-11"
    },
    {
      "id": "fsdax-617",
      "title": "Linux 6.17: Direct Access for files, page-cache bypass and file mappings.",
      "url": "https://docs.kernel.org/6.17/filesystems/dax.html",
      "accessed": "2026-11-11"
    },
    {
      "id": "hotplug-617",
      "title": "Linux 6.17: Memory Hotplug, online states and allocation zones.",
      "url": "https://docs.kernel.org/6.17/driver-api/cxl/linux/memory-hotplug.html",
      "accessed": "2026-11-11"
    },
    {
      "id": "daxctl-80",
      "title": "daxctl v80: reconfigure-device, destructive conversion and separate onlining.",
      "url": "https://github.com/pmem/ndctl/blob/v80/Documentation/daxctl/daxctl-reconfigure-device.txt",
      "accessed": "2026-11-11"
    },
    {
      "id": "types-617",
      "title": "Linux 6.17: CXL devices and protocols, volatile and persistent capacity.",
      "url": "https://docs.kernel.org/6.17/driver-api/cxl/devices/device-types.html",
      "accessed": "2026-11-11"
    }
  ],
  "updated": "2026-11-11",
  "provenance": [
    "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."
  ]
}
