From: Jens Axboe <axboe@kernel.dk>
To: tj@kernel.org, josef@toxicpanda.com,
Kemeng Shi <shikemeng@huaweicloud.com>
Cc: cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, shikemeng@huawei.com,
linfeilong@huawei.com, liuzhiqiang26@huawei.com
Subject: Re: [PATCH v3 0/9] A few bugfix and cleanup patches for blk-throttle
Date: Mon, 05 Dec 2022 13:46:07 -0700 [thread overview]
Message-ID: <167027316733.161635.16505872806618790217.b4-ty@kernel.dk> (raw)
In-Reply-To: <20221205115709.251489-1-shikemeng@huaweicloud.com>
On Mon, 05 Dec 2022 19:57:00 +0800, Kemeng Shi wrote:
> hierarchy, corret comment and so on. More details can be found in
> respective changelogs. Thanks.
>
Applied, thanks!
[1/9] blk-throttle: correct stale comment in throtl_pd_init
commit: f56019aef353576f43f945fdd065858145090582
[2/9] blk-throttle: Fix that bps of child could exceed bps limited in parent
commit: 84aca0a7e039c8735abc0f89f3f48e9006c0dfc7
[3/9] blk-throttle: ignore cgroup without io queued in blk_throtl_cancel_bios
commit: eb184791821409c37fef4f67638bb56bdaa82900
[4/9] blk-throttle: correct calculation of wait time in tg_may_dispatch
commit: 183daeb11de871b073515d14ec1e3bc0da79e038
[5/9] blk-throttle: simpfy low limit reached check in throtl_tg_can_upgrade
commit: a4d508e333829a8394e59efa06ce56e51f3e2b29
[6/9] blk-throttle: fix typo in comment of throtl_adjusted_limit
commit: 009df341714c6c20a44dd9268681a8bff10bb050
[7/9] blk-throttle: remove incorrect comment for tg_last_low_overflow_time
commit: e3031d4c7d2c5bff6b5944d61d4e31319739d216
[8/9] blk-throttle: remove repeat check of elapsed time from last upgrade in throtl_hierarchy_can_downgrade
commit: 9c9f209d9d81ea67cd84f53f470a592c252d845d
[9/9] blk-throttle: Use more siutable time_after check for update of slice_start
commit: eea3e8b74aa1648fc96b739458d067a6e498c302
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-12-05 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 11:57 Kemeng Shi
2022-12-05 11:57 ` [PATCH v3 1/9] blk-throttle: correct stale comment in throtl_pd_init Kemeng Shi
2022-12-05 20:43 ` Jens Axboe
2022-12-06 1:17 ` Kemeng Shi
2022-12-05 11:57 ` [PATCH v3 2/9] blk-throttle: Fix that bps of child could exceed bps limited in parent Kemeng Shi
2022-12-05 11:57 ` [PATCH v3 3/9] blk-throttle: ignore cgroup without io queued in blk_throtl_cancel_bios Kemeng Shi
2022-12-05 11:57 ` [PATCH v3 4/9] blk-throttle: correct calculation of wait time in tg_may_dispatch Kemeng Shi
2022-12-05 11:57 ` [PATCH v3 5/9] blk-throttle: simpfy low limit reached check in throtl_tg_can_upgrade Kemeng Shi
2022-12-05 11:57 ` [PATCH v3 6/9] blk-throttle: fix typo in comment of throtl_adjusted_limit Kemeng Shi
2022-12-05 11:57 ` [PATCH v3 7/9] blk-throttle: remove incorrect comment for tg_last_low_overflow_time Kemeng Shi
2022-12-05 11:57 ` [PATCH v3 8/9] blk-throttle: remove repeat check of elapsed time from last upgrade in throtl_hierarchy_can_downgrade Kemeng Shi
2022-12-05 11:57 ` [PATCH v3 9/9] blk-throttle: Use more siutable time_after check for update of slice_start Kemeng Shi
2022-12-05 20:46 ` 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=167027316733.161635.16505872806618790217.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linfeilong@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=shikemeng@huawei.com \
--cc=shikemeng@huaweicloud.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®