fio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Vincent Fu <vincentfu@gmail.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
	Niklas Cassel <niklas.cassel@wdc.com>,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [PATCH 0/2] fix loops option behavior of read-very workloads
Date: Wed, 14 Feb 2024 21:20:06 +0900	[thread overview]
Message-ID: <20240214122008.4123286-1-shinichiro.kawasaki@wdc.com> (raw)

After the commit 191d6634e8a6 ("verify: fix bytes_done accounting of
experimental verify") in fio version 3.33, loops option does not work
good with verify-read workloads. The first patch in this series fixes
it. The second patch adds a test case to confirm the fix.

Shin'ichiro Kawasaki (2):
  verify: fix loops option behavior of read-verify workloads
  test: add the test for loops option and read-verify workloads

 io_u.c             |  3 ++-
 t/jobs/t0029.fio   | 14 ++++++++++++++
 t/run-fio-tests.py | 21 +++++++++++++++++++++
 3 files changed, 37 insertions(+), 1 deletion(-)
 create mode 100644 t/jobs/t0029.fio

-- 
2.43.0


             reply	other threads:[~2024-02-14 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 12:20 Shin'ichiro Kawasaki [this message]
2024-02-14 12:20 ` [PATCH 1/2] verify: fix loops option behavior of read-verify workloads Shin'ichiro Kawasaki
2024-02-14 12:20 ` [PATCH 2/2] test: add the test for loops option and " Shin'ichiro Kawasaki
2024-02-14 14:39 ` [PATCH 0/2] fix loops option behavior of read-very workloads Jens Axboe

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=20240214122008.4123286-1-shinichiro.kawasaki@wdc.com \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=Dmitry.Fomichev@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=fio@vger.kernel.org \
    --cc=niklas.cassel@wdc.com \
    --cc=vincentfu@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).