From: Joel Granados <j.granados@samsung.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: <osandov@fb.com>, <joshi.k@samsung.com>, <anuj20.g@samsung.com>,
<ankit.kumar@samsung.com>, <vincent.fu@samsung.com>,
<ming.lei@redhat.com>, <linux-block@vger.kernel.org>
Subject: Re: [PATCH 1/6] common/fio: add helpers using io-uring cmd engine
Date: Fri, 30 Dec 2022 11:10:37 +0100 [thread overview]
Message-ID: <20221230101037.4g6tckvbtijteb26@localhost> (raw)
In-Reply-To: <20221221103441.3216600-2-mcgrof@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2539 bytes --]
On Wed, Dec 21, 2022 at 02:34:36AM -0800, Luis Chamberlain wrote:
> This will allow us to add tests which use the io-uring cmd engine,
> part of fio. They are inspired by the work by Anuj Gupta and
> Ankit Kumar which added sample fio files onto fio for this exact
> purpose.
>
> We can build on those to expand test coverage with elaborate tests.
>
> We don't specify the cmd to allow other types of io-uring cmd
> users to use this other than nvme.
>
> Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
> ---
> common/fio | 47 +++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 47 insertions(+)
>
> diff --git a/common/fio b/common/fio
> index bed76d555b2a..4da90804ed21 100644
> --- a/common/fio
> +++ b/common/fio
> @@ -184,6 +184,53 @@ _run_fio_verify_io() {
> rm -f local*verify*state
> }
>
> +_run_fio_rand_iouring_cmd() {
> + _run_fio --bs=4k --rw=randread --numjobs="$(nproc)" \
> + --ioengine=io_uring_cmd --iodepth=32 \
> + --thread=1 --stonewall=1 \
> + --name=reads "$@"
> +}
> +
> +_run_fio_verify_iouring_cmd_randwrite() {
> + _run_fio --bs=4k --rw=randwrite --numjobs="$(nproc)" \
> + --ioengine=io_uring_cmd --iodepth=32 \
> + --thread=1 --stonewall=1 \
> + --sqthread_poll=1 --sqthread_poll_cpu=0 \
> + --nonvectored=1 --registerfiles=1 \
> + --verify=crc32c \
> + --name=verify "$@"
> + rm -f local*verify*state
> +}
> +
> +_run_fio_verify_iouring_cmd_write_opts() {
> + _run_fio --bs=4k --rw=write --numjobs="$(nproc)" \
> + --ioengine=io_uring_cmd --iodepth=32 \
> + --thread=1 --stonewall=1 \
> + --sqthread_poll=1 --sqthread_poll_cpu=0 \
> + --nonvectored=1 --registerfiles=1 \
> + --verify=crc32c \
> + --name=verify "$@"
> + rm -f local*verify*state
> +}
> +
> +_run_fio_iouring_cmd_zone() {
> + _run_fio --rw=randread --numjobs="$(nproc)" \
> + --ioengine=io_uring_cmd --iodepth=1 \
> + --stonewall=1 \
> + --zonemode=zbd \
> + --name=reads "$@"
> +}
> +
> +_run_fio_verify_iouring_cmd_write_opts_zone() {
> + _run_fio --rw=randread --numjobs="$(nproc)" \
> + --ioengine=io_uring_cmd --iodepth=1 \
> + --stonewall=1 \
> + --zonemode=zbd \
> + --sqthread_poll=1 --registerfiles=1 --sqthread_poll_cpu=0 \
> + --verify=crc32c \
> + --name=verify "$@"
Are you missing a "rm -f local*verify*state" here?
Joel
> +}
> +
> _fio_perf_report() {
> # If there is more than one group, we don't know what to report.
> if [[ $(wc -l < "$TMPDIR/fio_perf") -gt 1 ]]; then
> --
> 2.35.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-12-30 10:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 10:34 [PATCH 0/6] blktests: char device tests with iouring-cmd fio Luis Chamberlain
2022-12-21 10:34 ` [PATCH 1/6] common/fio: add helpers using io-uring cmd engine Luis Chamberlain
2022-12-30 10:10 ` Joel Granados [this message]
2022-12-21 10:34 ` [PATCH 2/6] tests/nvme: add new test for rand-read on the nvme character device Luis Chamberlain
2022-12-23 13:11 ` Kanchan Joshi
2022-12-23 15:56 ` Luis Chamberlain
2023-01-17 7:46 ` Kanchan Joshi
2022-12-30 10:37 ` Joel Granados
2023-01-03 5:48 ` Chaitanya Kulkarni
2022-12-21 10:34 ` [PATCH 3/6] tests/nvme: add new test for rand-write " Luis Chamberlain
2022-12-21 10:34 ` [PATCH 4/6] tests/nvme: add new test for optimal write " Luis Chamberlain
2022-12-21 10:34 ` [PATCH 5/6] tests/zbd: add new basic test for reading zone " Luis Chamberlain
2022-12-21 10:34 ` [PATCH 6/6] " Luis Chamberlain
2022-12-28 3:25 ` [PATCH 0/6] blktests: char device tests with iouring-cmd fio Shinichiro Kawasaki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221230101037.4g6tckvbtijteb26@localhost \
--to=j.granados@samsung.com \
--cc=ankit.kumar@samsung.com \
--cc=anuj20.g@samsung.com \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=vincent.fu@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox