RE: [PATCH v2 5/8] docs: document options for io_uring_cmd I/O engine

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Ankit Kumar [mailto:ankit.kumar@xxxxxxxxxxx]
> Sent: Thursday, May 26, 2022 10:48 AM
> To: axboe@xxxxxxxxx
> Cc: fio@xxxxxxxxxxxxxxx; krish.reddy@xxxxxxxxxxx;
> joshi.k@xxxxxxxxxxx; anuj20.g@xxxxxxxxxxx; Ankit Kumar
> <ankit.kumar@xxxxxxxxxxx>
> Subject: [PATCH v2 5/8] docs: document options for io_uring_cmd I/O
> engine
> 
> Update documentation with io_uring_cmd I/O engine specific options.
> Add missing io_uring I/O engine entry from fio man page.
> Update docs with missing io_uring engine specific options.
> 
> Signed-off-by: Ankit Kumar <ankit.kumar@xxxxxxxxxxx>
> ---

> +.. option:: nonvectored : [io_uring] [io_uring_cmd]
> +
> +	With this option, fio will use non-vectored read/write commands,
> where
> +	address must contain the address directly.
> 
> -.. option:: registerfiles : [io_uring]
> +.. option:: force_async=int : [io_uring] [io_uring_cmd]
> +
> +	Normal operation for io_uring is to try and issue an sqe as
> +	non-blocking first, and if that fails, execute it in an async manner.
> +	With this option set to N, then every N request fio will ask sqe to
> +	be issued in an async manner.
> +

It would be helpful to state the default values for nonvectored and force_async.




[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux