Searched refs:DAX (Results 1 – 15 of 15) sorted by relevance
4 DAX Driver Operation11 The CXL subsystem depends on the DAX subsystem to either:16 The DAX subsystem exposes this ability through the `cxl_dax_region` driver.18 a `DAX Device`.20 DAX Device22 A `DAX Device` is a file-like interface exposed in :code:`/dev/daxN.Y`. A32 The :code:`dax_kmem` driver converts a `DAX Device` into a series of `hotplug37 The :code:`memmap_on_memory` setting (both global and DAX device local)
8 and how it is ultimately exposed to users as either a :code:`DAX` device or72 e) Regions surfaced as DAX region76 * DAX device created via DAX driver78 4) DAX Driver Operation80 a) DAX driver surfaces DAX region as one of two dax device modes84 * DAX kmem IO Resource creation90 b) DAX kmem surfaces memory region to Memory Hotplug to add to page
7 the `DAX` driver to surface a `Driver Managed` memory region via the73 The DAX driver surfaces this memory to memory-hotplug as "Driver Managed". This
406 on these devices to the DAX subsystem via a `DAX Region`.437 DAX Region439 A `DAX Region` is used to convert a CXL `Memory Region` to a DAX device. A440 DAX device may then be accessed directly via a file descriptor interface, or441 converted to System RAM via the DAX kmem driver. See the DAX driver section493 be surfaced as a DAX device - and therefore not be exposed to the page
4 DAX Devices6 CXL capacity exposed as a DAX device can be accessed directly via mmap.26 #define DEVICE_PATH "/dev/dax0.0" // Replace DAX device path33 /* Open the DAX device */
14 memory resource that may span multiple DIMMs and support DAX22 select DAX33 capable of DAX (direct-access) file system mappings. See78 bool "NVDIMM DAX: Raw access to persistent memory"86 accessed via DAX (mmap(2)).105 Allows creation of DAX devices on RAM carveouts.135 to debug an issue unrelated to NVDIMMs or DAX then say N to this
4 Device DAX
43 Verity and DAX are not compatible and attempts to set both of these flags
49 depends on DAX
52 memory as a DAX device and/or kmem.
152 NOTE: Some pages, such as DAX pages, cannot be pinned with longterm pins. That's153 because DAX pages do not have a separate page cache, and so "pinning" implies
635 DAX I/O
1234 "device-physical" addresses which is needed for DAX, PCI_P2PDMA, and
1238 - DAX (Direct Access) is not supported on encrypted files.
7443 DEVICE DIRECT ACCESS (DAX)7453 DEVICE DIRECT ACCESS (DAX) [fsdev_dax]10050 FILESYSTEM DIRECT ACCESS (DAX)