Home
last modified time | relevance | path

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

12

/openbmc/linux/fs/fuse/
H A Ddax.c187 struct fuse_conn_dax *fcd = fm->fc->dax; in fuse_setup_one_mapping()
223 interval_tree_insert(&dmap->itn, &fi->dax->tree); in fuse_setup_one_mapping()
224 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 DMakefile11 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.h172 struct fuse_inode_dax *dax; member
862 struct fuse_conn_dax *dax; member
/openbmc/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
/openbmc/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.rst79 dax
H A Dapi-summary.rst83 .. kernel-doc:: fs/dax.c
H A Derofs.rst120 dax={always,never} Use direct access (no page cache). See
121 Documentation/filesystems/dax.rst.
122 dax A legacy option which is an alias for ``dax=always``.
/openbmc/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"
/openbmc/linux/Documentation/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::
/openbmc/qemu/docs/
H A Dnvdimm.txt145 For device dax (e.g., /dev/dax0.0), this alignment needs to match the
146 alignment requirement of the device dax. The NUM of 'align=NUM' option
147 must be larger than or equal to the 'align' of device dax.
148 We can use one of the following commands to show the 'align' of device dax.
153 In order to get the proper 'align' of device dax, you need to install
156 For example, device dax require the 2 MB alignment, so we can use
170 B. DAX file(mounted with dax option)
213 mounted with the "dax" mount option:
217 mount -o dax /dev/pmem0p1 /mnt
/openbmc/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()
/openbmc/linux/Documentation/arch/sparc/
H A Dindex.rst11 oradax/oracle-dax
/openbmc/linux/Documentation/mm/
H A Dvmemmap_dedup.rst208 The device-dax interface uses the same tail deduplication technique explained
221 There's no remapping of vmemmap given that device-dax memory is not part of
224 the head vmemmap page representing, whereas device-dax reuses the tail
229 Here's how things look like on device-dax after the sections are populated::
/openbmc/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
/openbmc/linux/Documentation/admin-guide/mm/
H A Dshrinker_debugfs.rst37 sb-dax-11 sb-proc-45 sb-tmpfs-35
/openbmc/linux/fs/
H A DMakefile31 obj-$(CONFIG_FS_DAX) += dax.o
/openbmc/linux/drivers/
H A DMakefile81 obj-y += dax/
H A DKconfig214 source "drivers/dax/Kconfig"
/openbmc/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/
/openbmc/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
/openbmc/linux/drivers/nvdimm/
H A DKconfig82 Support raw device dax access to a persistent memory

12