-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
examples: add example and fiograph for protection information options
Add missing io_uring_cmd ioengine options to fiograph config. Add two example job files for the protection information options. These include one for DIF i.e. extended LBA data size, and the other for DIX i.e. separate metadata buffer case. Add the corresponding fiograph diagram for these. Signed-off-by: Ankit Kumar <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Vincent Fu <[email protected]>
- Loading branch information
1 parent
6795954
commit b311162
Showing
5 changed files
with
64 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Protection information test with io_uring_cmd I/O engine for nvme-ns generic | ||
# character device. | ||
# | ||
# This requires nvme device to be formatted with extended LBA data size and | ||
# protection information enabled. This can be done with nvme-cli utility. | ||
# Replace bs below with the correct extended LBA size. | ||
# | ||
# 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=4160 | ||
pi_act=0 | ||
pi_chk=GUARD,APPTAG,REFTAG | ||
apptag=0x0888 | ||
apptag_mask=0xFFFF | ||
thread=1 | ||
stonewall=1 | ||
|
||
[write] | ||
rw=write | ||
|
||
[read] | ||
rw=read |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# 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 |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters