From: Vincent Fu <vincentfu@gmail.com>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Cc: gost.dev@samsung.com
Subject: blog post on fio's verify feature
Date: Mon, 30 Jun 2025 15:42:01 -0400 [thread overview]
Message-ID: <e17fc881-c699-4d72-8824-0eceb69a7d3a@gmail.com> (raw)
I am pleased to share a blog post about fio's verify feature.
https://github.com/vincentkfu/fio-blog/wiki/Verify-overview
Ankit Kumar and I contributed some verify-related patches a few months
ago, and this blog post shares some of what is going on behind the
scenes in a verify workload.
Feedback is welcome.
Vincent
next reply other threads:[~2025-06-30 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 19:42 Vincent Fu [this message]
2025-07-01 15:11 ` blog post on fio's verify feature Adam Horshack
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=e17fc881-c699-4d72-8824-0eceb69a7d3a@gmail.com \
--to=vincentfu@gmail.com \
--cc=fio@vger.kernel.org \
--cc=gost.dev@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