public inbox for fio@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Jan Kara <jack@suse.cz>, fio@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, Vincent Fu <vincentfu@gmail.com>
Subject: Re: [PATCH 3/5] eta: Use in_ramp_period() instead of opencoding it
Date: Thu, 18 Dec 2025 07:55:09 +0900	[thread overview]
Message-ID: <95e9ba19-2753-4cda-b4e0-748c6687f317@kernel.org> (raw)
In-Reply-To: <20251217161722.6357-3-jack@suse.cz>

On 12/18/25 01:17, Jan Kara wrote:
> Signed-off-by: Jan Kara <jack@suse.cz>

Looks good.

Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2025-12-17 22:55 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 ` [PATCH 3/5] eta: Use in_ramp_period() instead of opencoding it Jan Kara
2025-12-17 22:55   ` Damien Le Moal [this message]
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=95e9ba19-2753-4cda-b4e0-748c6687f317@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jack@suse.cz \
    --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