6 tristate "DAX: direct access to differentiated memory"
8 default m if NVDIMM_DAX
13 tristate "Device DAX: direct access mapping device"
14 depends on TRANSPARENT_HUGEPAGE
16 Support raw access to differentiated (persistence, bandwidth,
17 latency...) memory via an mmap(2) capable character
18 device. Platform firmware or a device driver may identify a
19 platform memory resource that is differentiated from the
20 baseline memory pool. Mappings of a /dev/daxX.Y device impose
21 restrictions that make the mapping behavior deterministic.
24 tristate "PMEM DAX: direct access to persistent memory"
25 depends on LIBNVDIMM && NVDIMM_DAX && DEV_DAX
26 depends on m # until we can kill DEV_DAX_PMEM_COMPAT
29 Support raw access to persistent memory. Note that this
30 driver consumes memory ranges allocated and exported by the
36 tristate "KMEM DAX: volatile-use of persistent memory"
39 depends on MEMORY_HOTPLUG # for add_memory() and friends
41 Support access to persistent memory as if it were RAM. This
42 allows easier use of persistent memory by unmodified
45 To use this feature, a DAX device must be unbound from the
46 device_dax driver (PMEM DAX) and bound to this kmem driver
51 config DEV_DAX_PMEM_COMPAT
52 tristate "PMEM DAX: support the deprecated /sys/class/dax interface"
53 depends on DEV_DAX_PMEM
56 Older versions of the libdaxctl library expect to find all
57 device-dax instances under /sys/class/dax. If libdaxctl in
58 your distribution is older than v58 say M, otherwise say N.