From: Jeff Moyer <jmoyer@redhat.com>
To: Giuliano G Motter <mottergiuliano@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: How do I characterize my usecase so that I can simulate it with fio the closest?
Date: Mon, 20 Jan 2025 14:46:32 -0500 [thread overview]
Message-ID: <x498qr5mfon.fsf@segfault.usersys.redhat.com> (raw)
In-Reply-To: <CAK0q08N-yCNKK9Jsg5h2_Kmm9iEhc95fPuGxYYC-BhK8dkeboQ@mail.gmail.com> (Giuliano G. Motter's message of "Mon, 20 Jan 2025 08:58:40 -0300")
Giuliano G Motter <mottergiuliano@gmail.com> writes:
> At a second moment, tough, I would in fact like to implement a test
> that is the closest as possible to the real process we have during USB
> stick flashing
>
> Question:
> How do I characterize my use case so that I can simulate it with fio?
Have you tried the btrecord and btreplay utilities shipped with
blktrace? Or, if you are set on using fio, you can replay blktraces
using fio. See the fio(1) man page section on "I/O replay".
Good luck,
Jeff
prev parent reply other threads:[~2025-01-20 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 11:58 How do I characterize my usecase so that I can simulate it with fio the closest? Giuliano G Motter
2025-01-20 19:46 ` Jeff Moyer [this message]
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=x498qr5mfon.fsf@segfault.usersys.redhat.com \
--to=jmoyer@redhat.com \
--cc=fio@vger.kernel.org \
--cc=mottergiuliano@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