Commit | Line | Data |
---|---|---|
104ee4de DJ |
1 | [global] |
2 | bs=2m | |
3 | ioengine=dev-dax | |
4 | norandommap | |
5 | time_based=1 | |
6 | runtime=30 | |
7 | group_reporting | |
8 | disable_lat=1 | |
9 | disable_slat=1 | |
10 | disable_clat=1 | |
11 | clat_percentiles=0 | |
12 | cpus_allowed_policy=split | |
13 | ||
14 | # For the dev-dax engine: | |
15 | # | |
16 | # IOs always complete immediately | |
17 | # IOs are always direct | |
18 | # | |
19 | iodepth=1 | |
20 | direct=0 | |
21 | thread=1 | |
22 | numjobs=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 | # | |
37 | filename=/dev/dax0.0 | |
38 | ||
39 | [dev-dax-write] | |
40 | rw=randwrite | |
41 | stonewall | |
42 | ||
43 | [dev-dax-read] | |
44 | rw=randread | |
45 | stonewall |