Home
last modified time | relevance | path

Searched refs:dax (Results 1 – 25 of 40) sorted by relevance

12

/linux/Documentation/ABI/testing/
H A Dsysfs-bus-dax1 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/fs/fuse/
H A Ddax.c186 struct fuse_conn_dax *fcd = fm->fc->dax; in fuse_setup_one_mapping()
222 interval_tree_insert(&dmap->itn, &fi->dax->tree); in fuse_setup_one_mapping()
223 fi->dax->nr++; in fuse_setup_one_mapping()
322 node = interval_tree_iter_first(&fi->dax->tree, start_idx, in inode_reclaim_dmap_range()
329 interval_tree_remove(&dmap->itn, &fi->dax->tree); in inode_reclaim_dmap_range()
338 WARN_ON(fi->dax->nr < num); in inode_reclaim_dmap_range()
339 fi->dax->nr -= num; in inode_reclaim_dmap_range()
384 inode_reclaim_dmap_range(fc->dax, inode, 0, -1); in fuse_dax_inode_cleanup()
385 WARN_ON(fi->dax->nr); in fuse_dax_inode_cleanup()
437 struct fuse_conn_dax *fcd = fc->dax; in fuse_setup_new_dax_mapping()
[all …]
H A DMakefile16 fuse-$(CONFIG_FUSE_DAX) += dax.o
H A DKconfig54 If you want to allow mounting a Virtio Filesystem with the "dax"
/linux/Documentation/filesystems/
H A Ddax.rst32 When mounting the filesystem, use the ``-o dax`` option on the command line or
33 add 'dax' to the options in ``/etc/fstab``. This works to enable `DAX` on all files
34 within the filesystem. It is equivalent to the ``-o dax=always`` behavior below.
57 4. There exist dax mount options which can override `FS_XFLAG_DAX` in the
61 ``-o dax=inode`` means "follow `FS_XFLAG_DAX`" and is the default.
63 ``-o dax=never`` means "never set `S_DAX`, ignore `FS_XFLAG_DAX`."
65 ``-o dax=always`` means "always set `S_DAX` ignore `FS_XFLAG_DAX`."
67 ``-o dax`` is a legacy option which is an alias for ``dax=always``.
71 The option ``-o dax`` may be removed in the future so ``-o dax=always`` is
77 the same even when the filesystem is mounted with a dax option. However,
[all …]
H A Dindex.rst82 dax
H A Dapi-summary.rst83 .. kernel-doc:: fs/dax.c
H A Derofs.rst124 dax={always,never} Use direct access (no page cache). See
125 Documentation/filesystems/dax.rst.
126 dax A legacy option which is an alias for ``dax=always``.
/linux/tools/testing/nvdimm/
H A DKbuild23 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 DMakefile2 obj-$(CONFIG_DAX) += dax.o
8 dax-y := super.o
9 dax-y += bus.o
H A DKconfig40 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 Dvmemmap_dedup.rst7 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 Doverview.rst80 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 Ddax-driver.rst23 memory region exposed via dax device can be accessed via userland software
H A Dmemory-hotplug.rst55 - :code:`/sys/bus/dax/devices/daxN.Y/memmap_on_memory`
/linux/Documentation/driver-api/cxl/
H A Dindex.rst42 linux/dax-driver
50 allocation/dax
/linux/Documentation/arch/sparc/
H A Dindex.rst11 oradax/oracle-dax
/linux/Documentation/mm/
H A Dvmemmap_dedup.rst188 The device-dax interface uses the same tail deduplication technique explained
201 There's no remapping of vmemmap given that device-dax memory is not part of
204 the head vmemmap page representing, whereas device-dax reuses the tail
209 Here's how things look like on device-dax after the sections are populated::
/linux/Documentation/arch/sparc/oradax/
H A Doracle-dax.rst25 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
/linux/Documentation/driver-api/cxl/allocation/
H A Ddax.rst14 Note that mappings must be aligned (size and base) to the dax device's base
/linux/Documentation/admin-guide/mm/
H A Dshrinker_debugfs.rst37 sb-dax-11 sb-proc-45 sb-tmpfs-35
/linux/drivers/
H A DMakefile78 obj-y += dax/
H A DKconfig224 source "drivers/dax/Kconfig"
/linux/fs/
H A DMakefile32 obj-$(CONFIG_FS_DAX) += dax.o
/linux/Documentation/driver-api/media/drivers/
H A Dpvrusb2.rst14 Danielsson <pvrusb2@dax.nu> whose web page can be found here:
15 http://pvrusb2.dax.nu/

12