From: Jan Kara <jack@suse.cz>
To: fio@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, Vincent Fu <vincentfu@gmail.com>,
Jan Kara <jack@suse.cz>
Subject: [PATCH 3/5] eta: Use in_ramp_period() instead of opencoding it
Date: Wed, 17 Dec 2025 17:17:13 +0100 [thread overview]
Message-ID: <20251217161722.6357-3-jack@suse.cz> (raw)
In-Reply-To: <20251217160217.15533-1-jack@suse.cz>
Signed-off-by: Jan Kara <jack@suse.cz>
---
eta.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/eta.c b/eta.c
index 947752b9dc17..c6e3cffb81d6 100644
--- a/eta.c
+++ b/eta.c
@@ -274,9 +274,8 @@ static unsigned long thread_eta(struct thread_data *td)
uint64_t ramp_time = td->o.ramp_time;
t_eta = __timeout + start_delay;
- if (!td->ramp_period_over) {
+ if (in_ramp_period(td))
t_eta += ramp_time;
- }
t_eta /= 1000000ULL;
if ((td->runstate == TD_RAMP) && in_ramp_period(td)) {
--
2.51.0
next prev parent reply other threads:[~2025-12-17 16:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 16:17 [PATCH 0/5] Add support for specifying ramp up period by amount of IO Jan Kara
2025-12-17 16:17 ` [PATCH 1/5] time: rename in_ramp_time() and ramp_time_over() Jan Kara
2025-12-17 22:52 ` Damien Le Moal
2025-12-19 3:53 ` fiotestbot
2025-12-17 16:17 ` [PATCH 2/5] td: Initialize ramp_period_over based on options Jan Kara
2025-12-17 22:53 ` Damien Le Moal
2025-12-17 16:17 ` Jan Kara [this message]
2025-12-17 22:55 ` [PATCH 3/5] eta: Use in_ramp_period() instead of opencoding it Damien Le Moal
2025-12-17 16:17 ` [PATCH 4/5] time: Evaluate ramp up condition once per second Jan Kara
2025-12-17 22:58 ` Damien Le Moal
2025-12-17 16:17 ` [PATCH 5/5] Add option to specify ramp period by amount of IO Jan Kara
2025-12-17 22:56 ` Jens Axboe
2025-12-18 17:18 ` Jan Kara
2025-12-17 23:03 ` Damien Le Moal
2025-12-18 16:31 ` Jan Kara
2025-12-19 8:12 ` Damien Le Moal
2025-12-19 13:10 ` Jan Kara
2025-12-18 15:19 ` Vincent Fu
2025-12-18 17:18 ` Jan Kara
2025-12-18 21:42 ` 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=20251217161722.6357-3-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