All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, Zizhi Wo <wozizhi@huaweicloud.com>
Cc: yangerkun@huawei.com, yukuai3@huawei.com, ming.lei@redhat.com,
	 tj@kernel.org
Subject: Re: [PATCH V5 0/7] blk-throttle: Split the blkthrotl queue to solve the IO delay issue
Date: Tue, 13 May 2025 14:47:25 -0600	[thread overview]
Message-ID: <174716924503.10749.10556592372517387859.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250506020935.655574-1-wozizhi@huaweicloud.com>


On Tue, 06 May 2025 10:09:27 +0800, Zizhi Wo wrote:
> Changes since V4:
> Patch 6 was modified to resolve the conflict.
> 
> Changes since V1-3:
> 1) Updated the comments in patches 4 and 6 for greater specificity.
> 2) In patch 6, replaced the @queued parameter with @sq in both
> throtl_qnode_add_bio and throtl_pop_queued to facilitate internal changes.
> And the potential problem of null pointer dereference has been fixed.
> 
> [...]

Applied, thanks!

[1/7] blk-throttle: Rename tg_may_dispatch() to tg_dispatch_time()
      commit: fd6c08b26460436ec0f53e125f8ded98738806f1
[2/7] blk-throttle: Refactor tg_dispatch_time by extracting tg_dispatch_bps/iops_time
      commit: 3660cd4228d9330b618e2700491891f08824011d
[3/7] blk-throttle: Split throtl_charge_bio() into bps and iops functions
      commit: a404be5399d762f5737a4a731b42a38f552f2b44
[4/7] blk-throttle: Introduce flag "BIO_TG_BPS_THROTTLED"
      commit: c4da7bf54b1f76e7c5c8cc6d1c4db8b19af67c5d
[5/7] blk-throttle: Split the blkthrotl queue
      commit: f2c4902bd08b854a23c3c2ab352382fd7eef959f
[6/7] blk-throttle: Split the service queue
      commit: 28ad83b774a6f11126d45bf912bb8a7c16cb2b2b
[7/7] blk-throttle: Prevents the bps restricted io from entering the bps queue again
      commit: d1ba22ab2becc8bf84d466791b970905abe99b23

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2025-05-13 20:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06  2:09 [PATCH V5 0/7] blk-throttle: Split the blkthrotl queue to solve the IO delay issue Zizhi Wo
2025-05-06  2:09 ` [PATCH V5 1/7] blk-throttle: Rename tg_may_dispatch() to tg_dispatch_time() Zizhi Wo
2025-05-06  2:09 ` [PATCH V5 2/7] blk-throttle: Refactor tg_dispatch_time by extracting tg_dispatch_bps/iops_time Zizhi Wo
2025-05-06  2:09 ` [PATCH V5 3/7] blk-throttle: Split throtl_charge_bio() into bps and iops functions Zizhi Wo
2025-05-06  2:09 ` [PATCH V5 4/7] blk-throttle: Introduce flag "BIO_TG_BPS_THROTTLED" Zizhi Wo
2025-05-06  2:09 ` [PATCH V5 5/7] blk-throttle: Split the blkthrotl queue Zizhi Wo
2025-05-06  2:09 ` [PATCH V5 6/7] blk-throttle: Split the service queue Zizhi Wo
2025-05-15 13:08   ` Aishwarya
2025-05-15 13:39     ` Jens Axboe
2025-05-15 13:47       ` Zizhi Wo
2025-05-15 13:49         ` Jens Axboe
2025-05-06  2:09 ` [PATCH V5 7/7] blk-throttle: Prevents the bps restricted io from entering the bps queue again Zizhi Wo
2025-05-12  1:20 ` [PATCH V5 0/7] blk-throttle: Split the blkthrotl queue to solve the IO delay issue Zizhi Wo
2025-05-13 20:47 ` 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=174716924503.10749.10556592372517387859.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=tj@kernel.org \
    --cc=wozizhi@huaweicloud.com \
    --cc=yangerkun@huawei.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.