| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-dax | 1 What: /sys/bus/dax/devices/daxX.Y/align 6 (RW) Provides a way to specify an alignment for a dax device. 8 that back the dax device, and also by arch requirements. 10 What: /sys/bus/dax/devices/daxX.Y/mapping 15 (WO) Provides a way to allocate a mapping range under a dax 18 What: /sys/bus/dax/devices/daxX.Y/mapping[0..N]/start 19 What: /sys/bus/dax/devices/daxX.Y/mapping[0..N]/end 20 What: /sys/bus/dax/devices/daxX.Y/mapping[0..N]/page_offset 25 (RO) A dax device may have multiple constituent discontiguous 31 range in the dax device. [all …]
|
| /linux/tools/testing/nvdimm/ |
| H A D | Kbuild | 23 DAX_SRC := $(DRIVERS)/dax 33 obj-$(CONFIG_DAX) += dax.o 45 nd_pmem-y += pmem-dax.o 55 dax-y := $(DAX_SRC)/super.o 56 dax-y += $(DAX_SRC)/bus.o 57 dax-y += config_check.o 60 device_dax-y += dax-dev.o
|
| /linux/drivers/dax/ |
| H A D | Makefile | 2 obj-$(CONFIG_DAX) += dax.o 8 dax-y := super.o 9 dax-y += bus.o
|
| H A D | Kconfig | 40 device-dax instances for these memory ranges, and that also 55 after boot by the CXL driver. In the latter two cases a device-dax 65 tristate "KMEM DAX: map dax-devices as System-RAM"
|
| /linux/Documentation/arch/powerpc/ |
| H A D | vmemmap_dedup.rst | 7 The device-dax interface uses the tail deduplication technique explained in 22 Here's how things look like on device-dax after the sections are populated:: 50 Here's how things look like on device-dax after the sections are populated:: 79 Here's how things look like on device-dax after the sections are populated::
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | overview.rst | 80 a) DAX driver surfaces DAX region as one of two dax device modes 82 * kmem - dax device is converted to hotplug memory blocks 86 * hmem - dax device is left as daxdev to be accessed as a file. 95 a) mhp component surfaces a dax device memory region as multiple memory
|
| H A D | dax-driver.rst | 23 memory region exposed via dax device can be accessed via userland software
|
| H A D | memory-hotplug.rst | 55 - :code:`/sys/bus/dax/devices/daxN.Y/memmap_on_memory`
|
| H A D | early-boot.rst | 40 converted to a dax device should be managed (left as DAX or onlined as
|
| /linux/Documentation/driver-api/cxl/ |
| H A D | index.rst | 41 linux/dax-driver 49 allocation/dax
|
| /linux/Documentation/arch/sparc/ |
| H A D | index.rst | 11 oradax/oracle-dax
|
| /linux/fs/fuse/ |
| H A D | Makefile | 16 fuse-$(CONFIG_FUSE_DAX) += dax.o
|
| H A D | Kconfig | 54 If you want to allow mounting a Virtio Filesystem with the "dax"
|
| H A D | fuse_i.h | 212 struct fuse_inode_dax *dax; member 971 struct fuse_conn_dax *dax; member
|
| /linux/Documentation/arch/sparc/oradax/ |
| H A D | oracle-dax.rst | 25 the accompanying document, dax-hv-api.txt, which is a plain text 184 - open dax device 193 - close the dax device 250 each of these fields, and see dax-hv-api.txt for a complete description 383 completion area, closing the dax device, freeing memory etc. 399 The dax submit hypercall is made directly. The flags used in the 444 .. include:: dax-hv-api.txt
|
| H A D | dax-hv-api.txt | 51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility 81 36.1.1.2. "ORCL,sun4v-dax-fc" Device Compatibility 82 … "ORCL,sun4v-dax-fc" is compatible with the "ORCL,sun4v-dax" interface, and includes additional CCB 497 dax-fc" compatible virtual device variants) 1299 ret3 dax 1332 … The dax return value is only valid when the state is ENQUEUED. The value returned is the DAX unit
|
| /linux/Documentation/driver-api/cxl/allocation/ |
| H A D | dax.rst | 14 Note that mappings must be aligned (size and base) to the dax device's base
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | shrinker_debugfs.rst | 37 sb-dax-11 sb-proc-45 sb-tmpfs-35
|
| /linux/fs/ |
| H A D | Makefile | 32 obj-$(CONFIG_FS_DAX) += dax.o
|
| /linux/drivers/ |
| H A D | Makefile | 78 obj-y += dax/
|
| H A D | Kconfig | 224 source "drivers/dax/Kconfig"
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | pvrusb2.rst | 14 Danielsson <pvrusb2@dax.nu> whose web page can be found here: 15 http://pvrusb2.dax.nu/
|
| /linux/drivers/firmware/efi/ |
| H A D | Kconfig | 42 resource, and set aside for direct-access (device-dax) by 45 device-dax kmem facility. Say N to have the kernel treat this
|
| /linux/drivers/nvdimm/ |
| H A D | Kconfig | 82 Support raw device dax access to a persistent memory
|
| /linux/Documentation/filesystems/ |
| H A D | ext2.rst | 27 dax Use direct access (no page cache). See 28 Documentation/filesystems/dax.rst.
|