1[global] 2bs=2m 3ioengine=dev-dax 4norandommap 5time_based=1 6runtime=30 7group_reporting 8disable_lat=1 9disable_slat=1 10disable_clat=1 11clat_percentiles=0 12cpus_allowed_policy=split 13 14# For the dev-dax engine: 15# 16# IOs always complete immediately 17# IOs are always direct 18# 19iodepth=1 20direct=0 21thread=1 22numjobs=16 23# 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. 30# 31# Check the alignment requirement of your DAX device. Currently the default 32# should be 2M. Blocksize (bs) should meet alignment requirement. 33# 34# An example of creating a dev dax device node from pmem: 35# ndctl create-namespace --reconfig=namespace0.0 --mode=dax --force 36# 37filename=/dev/dax0.0 38 39[dev-dax-write] 40rw=randwrite 41stonewall 42 43[dev-dax-read] 44rw=randread 45stonewall 46