From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>
Cc: Tejun Heo <tj@kernel.org>, Josef Bacik <josef@toxicpanda.com>,
Yu Kuai <yukuai3@huawei.com>
Subject: Re: [PATCH 0/3] blk-throttle: remove last_bytes/ios and carryover byte/ios
Date: Wed, 05 Mar 2025 16:25:09 -0700 [thread overview]
Message-ID: <174121710911.165456.3433159135540117935.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250305043123.3938491-1-ming.lei@redhat.com>
On Wed, 05 Mar 2025 12:31:18 +0800, Ming Lei wrote:
> Remove last_bytes_disp and last_ios_disp which isn't used any more.
>
> Remove carryover bytes/ios because we can carry the compensation bytes/ios
> against dispatch bytes/ios directly.
>
> Depends on "[PATCH v2] blk-throttle: fix lower bps rate by throtl_trim_slice()"[1]
>
> [...]
Applied, thanks!
[1/3] blk-throttle: remove last_bytes_disp and last_ios_disp
commit: 483a393e7e6189aac7d47b5295029159ab7a1cf1
[2/3] blk-throttle: don't take carryover for prioritized processing of metadata
commit: a9fc8868b350cbf4ff730a4ea9651319cc669516
[3/3] blk-throttle: carry over directly
commit: 6cc477c36875ea5329b8bfbdf4d91f83dc653c91
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-03-05 23:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 4:31 [PATCH 0/3] blk-throttle: remove last_bytes/ios and carryover byte/ios Ming Lei
2025-03-05 4:31 ` [PATCH 1/3] blk-throttle: remove last_bytes_disp and last_ios_disp Ming Lei
2025-03-05 19:07 ` Tejun Heo
2025-03-05 4:31 ` [PATCH 2/3] blk-throttle: don't take carryover for prioritized processing of metadata Ming Lei
2025-03-05 19:11 ` Tejun Heo
2025-03-05 4:31 ` [PATCH 3/3] blk-throttle: carry over directly Ming Lei
2025-03-05 19:16 ` Tejun Heo
2025-04-11 2:53 ` Yu Kuai
2025-04-11 15:01 ` Ming Lei
2025-04-12 0:37 ` Yu Kuai
2025-04-14 2:32 ` Ming Lei
2025-04-14 11:47 ` Yu Kuai
2025-03-05 23:25 ` Jens Axboe [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=174121710911.165456.3433159135540117935.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=tj@kernel.org \
--cc=yukuai3@huawei.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