12 cpus_allowed_policy=split
14 # For the dev-dax engine:
16 # IOs always complete immediately
17 # IOs are always direct
24 # The dev-dax engine does IO to DAX device that are special character
25 # devices exported by the kernel (e.g. /dev/dax0.0). The device is
26 # opened normally and then the region is accessible via mmap. We do
27 # not use the O_DIRECT flag because the device is naturally direct
28 # access. The O_DIRECT flags will result in failure. The engine
29 # access the underlying NVDIMM directly once the mmapping is setup.
31 # Check the alignment requirement of your DAX device. Currently the default
32 # should be 2M. Blocksize (bs) should meet alignment requirement.
34 # An example of creating a dev dax device node from pmem:
35 # ndctl create-namespace --reconfig=namespace0.0 --mode=dax --force