[fio.git] / examples / uring-cmd-pi-sb.fio

# Protection information test with io_uring_cmd I/O engine for nvme-ns generic
# character device.
#
# This requires nvme device to be formatted with separate metadata buffer and
# protection information enabled. This can be done with nvme-cli utility.
# Replace md_per_io_size as per the required metadata buffer size for each IO.
#
# First we sequentially write to the device, without protection information
# action being set. FIO will generate and send necessary protection
# information data as per the protection information check option. Later on we
# sequentially read and verify the device returned protection information data.
#
[global]
filename=/dev/ng0n1
ioengine=io_uring_cmd
cmd_type=nvme
size=1G
iodepth=32
bs=4096
md_per_io_size=64
pi_act=0
pi_chk=GUARD,APPTAG,REFTAG
apptag=0x0888
apptag_mask=0xFFFF
thread=1
stonewall=1

[write]
rw=write

[read]
rw=read
Commit	Line	Data
b311162c AK	1	# Protection information test with io_uring_cmd I/O engine for nvme-ns generic
	2	# character device.
	3	#
	4	# This requires nvme device to be formatted with separate metadata buffer and
	5	# protection information enabled. This can be done with nvme-cli utility.
	6	# Replace md_per_io_size as per the required metadata buffer size for each IO.
	7	#
	8	# First we sequentially write to the device, without protection information
	9	# action being set. FIO will generate and send necessary protection
	10	# information data as per the protection information check option. Later on we
	11	# sequentially read and verify the device returned protection information data.
	12	#
	13	[global]
	14	filename=/dev/ng0n1
	15	ioengine=io_uring_cmd
	16	cmd_type=nvme
	17	size=1G
	18	iodepth=32
	19	bs=4096
	20	md_per_io_size=64
	21	pi_act=0
	22	pi_chk=GUARD,APPTAG,REFTAG
	23	apptag=0x0888
	24	apptag_mask=0xFFFF
	25	thread=1
	26	stonewall=1
	27
	28	[write]
	29	rw=write
	30
	31	[read]
	32	rw=read