From: Jan Kara <jack@suse.cz>
To: Vincent Fu <vincentfu@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
fio@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: [PATCH v2 0/5] Add support for specifying ramp up period by amount of IO
Date: Fri, 19 Dec 2025 14:42:34 +0100 [thread overview]
Message-ID: <20251219133853.8548-1-jack@suse.cz> (raw)
Hello!
In some cases the ramp up period is not easy to define by amount of time. This
is for example a case of buffered writes measurement where we want to start
measuring only once dirty throttling kicks in. The time until dirty throttling
kicks in depends on dirty limit (easy to figure out) and speed of writes to the
page cache (difficult to know in advance). This patch series adds to fio an
option to specify ramp up period in terms of amount to IO - i.e., the ramp up
period finishes once given amount of IO is done.
Changes since v1:
* Improved documentation to explain behavior with group reporting, replace wrong
note about default unit being megabytes
* Add sanity checks for inconsistent ramp_size values within reporting group
and usage of both ramp_size and ramp_time for a single job.
* Fix fio server support for the new option
Honza
Previous versions:
Link: http://lore.kernel.org/r/20251217160217.15533-1-jack@suse.cz # v1
next reply other threads:[~2025-12-19 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 13:42 Jan Kara [this message]
2025-12-19 13:42 ` [PATCH v2 1/5] time: rename in_ramp_time() and ramp_time_over() Jan Kara
2025-12-19 13:42 ` [PATCH v2 2/5] td: Initialize ramp_period_over based on options Jan Kara
2025-12-19 13:42 ` [PATCH v2 3/5] eta: Use in_ramp_period() instead of opencoding it Jan Kara
2025-12-19 13:42 ` [PATCH v2 4/5] time: Evaluate ramp up condition once per second Jan Kara
2025-12-19 13:42 ` [PATCH v2 5/5] Add option to specify ramp period by amount of IO Jan Kara
2025-12-24 19:44 ` [PATCH v2 0/5] Add support for specifying ramp up " Vincent Fu
2026-01-07 17:02 ` Jan Kara
2026-01-07 21:26 ` Vincent Fu
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=20251219133853.8548-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--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