Home
last modified time | relevance | path

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

12

/linux/Documentation/ABI/testing/
H A Dsysfs-bus-dax1 What: /sys/bus/dax/devices/daxX.Y/align
8 that back the dax device, and also by arch requirements.
10 What: /sys/bus/dax/devices/daxX.Y/mapping
18 What: /sys/bus/dax/devices/daxX.Y/mapping[0..N]/start
19 What: /sys/bus/dax/devices/daxX.Y/mapping[0..N]/end
31 range in the dax device.
33 What: /sys/bus/dax/devices/daxX.Y/resource
43 What: /sys/bus/dax/devices/daxX.Y/size
53 What: /sys/bus/dax/devices/daxX.Y/numa_node
62 What: /sys/bus/dax/devices/daxX.Y/target_node
[all …]
/linux/fs/fuse/
H A Ddax.c224 fi->dax->nr++; in fuse_setup_one_mapping()
905 fi->dax->nr--; in reclaim_one_dmap_locked()
1222 if (fc->dax) { in fuse_dax_conn_free()
1224 kfree(fc->dax); in fuse_dax_conn_free()
1225 fc->dax = NULL; in fuse_dax_conn_free()
1304 fc->dax = fcd; in fuse_dax_conn_alloc()
1312 fi->dax = NULL; in fuse_dax_inode_alloc()
1313 if (fc->dax) { in fuse_dax_inode_alloc()
1314 fi->dax = kzalloc(sizeof(*fi->dax), GFP_KERNEL_ACCOUNT); in fuse_dax_inode_alloc()
1315 if (!fi->dax) in fuse_dax_inode_alloc()
[all …]
H A DMakefile12 fuse-$(CONFIG_FUSE_DAX) += dax.o
H A DKconfig53 If you want to allow mounting a Virtio Filesystem with the "dax"
H A Dfuse_i.h188 struct fuse_inode_dax *dax; member
907 struct fuse_conn_dax *dax; member
/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/Documentation/filesystems/
H A Ddax.rst61 ``-o dax=inode`` means "follow `FS_XFLAG_DAX`" and is the default.
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
86 b) Setting the appropriate dax="foo" mount option
126 dax: a,e
127 no dax: b,c,d
139 dax: a,b,c,d
140 no dax:
152 dax: c,d
153 no dax: a,b
[all …]
H A Dindex.rst81 dax
H A Dapi-summary.rst80 .. 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/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/mm/
H A Dtruncate.c63 bool dax; in truncate_folio_batch_exceptionals() local
76 dax = dax_mapping(mapping); in truncate_folio_batch_exceptionals()
77 if (!dax) { in truncate_folio_batch_exceptionals()
91 if (unlikely(dax)) { in truncate_folio_batch_exceptionals()
99 if (!dax) { in truncate_folio_batch_exceptionals()
/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
H A Ddax-hv-api.txt51 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/admin-guide/mm/
H A Dshrinker_debugfs.rst37 sb-dax-11 sb-proc-45 sb-tmpfs-35
/linux/fs/
H A DMakefile31 obj-$(CONFIG_FS_DAX) += dax.o
/linux/drivers/
H A DMakefile75 obj-y += dax/
H A DKconfig214 source "drivers/dax/Kconfig"
/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/
/linux/drivers/nvdimm/
H A DKconfig82 Support raw device dax access to a persistent memory
/linux/drivers/firmware/efi/
H A DKconfig42 resource, and set aside for direct-access (device-dax) by
45 device-dax kmem facility. Say N to have the kernel treat this

12