Skip to content

Io uring/multiple write modes#2089

Open
minwooim wants to merge 2 commits into
axboe:masterfrom
minwooim:io_uring/multiple-write-modes
Open

Io uring/multiple write modes#2089
minwooim wants to merge 2 commits into
axboe:masterfrom
minwooim:io_uring/multiple-write-modes

Conversation

@minwooim
Copy link
Copy Markdown
Contributor

Introduce multiple wmode(write_mode) options for DDIR_WRITE workload.

@minwooim minwooim force-pushed the io_uring/multiple-write-modes branch 2 times, most recently from 63aaaae to 955c909 Compare May 17, 2026 22:45
minwooim added 2 commits May 18, 2026 07:47
Previously, `--write_mode=` takes one of either write, uncor, zeroes and
verify by replacing all the WRITE commands to the given commands.  This
option replaces all writes issued by a job with a single write type
command defined by write_mode, which limits flexibility.

This patch supports mixed `--write_mode=` within a job based on the
given ratio of each write family command.

Usage:
	--write_mode=30:write/20:zeroes/uncor:50

fio provides independent workloads on a per-job (thread_data) basis.
Issuing multiple write family commands previously required configuring
multiple jobs, which was cumbersome. This patch allows a single job to
exercise a variety of write commands.

Signed-off-by: Minwoo Im <minwoo.im@samsung.com>
If WRITE command zeroed out to specific offest, it should be verified as
zero just like trimmed.  If WRITE command errored to specific offset,
verify phase should be aware that the offset has been errored and error
will be coming expectedly.

This patch added two flags for @io_u and @ipo to represent that the
offset is errored or zeroed so that verify phase can verify them
accordingly.

Signed-off-by: Minwoo Im <minwoo.im@samsung.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant