From: Kemeng Shi <shikemeng@huawei.com>
To: <tj@kernel.org>, <josef@toxicpanda.com>, <axboe@kernel.dk>
Cc: <cgroups@vger.kernel.org>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] A few cleanup and bugfix patches for blk-iocost
Date: Wed, 23 Nov 2022 14:09:14 +0800 [thread overview]
Message-ID: <5ae7f0a0-8540-bbfe-2fe7-b18fc071ae1c@huawei.com> (raw)
In-Reply-To: <20221018121932.10792-1-shikemeng@huawei.com>
Friendly ping
on 10/18/2022 8:19 PM, Kemeng Shi wrote:
> This series contain a few patch to correct comment, correct trace of
> vtime_rate and so on. More detail can be found in the respective
> changelogs.
>
> ---
> v2:
> Thanks Tejun for review and comment!
> Add Acked-by tag from Tejun.
> Correct description in patch 3/5 and 4/5.
> Drop "blk-iocost: Avoid to call current_hweight_max if iocg->inuse
> == iocg->active"
> Drop "blk-iocost: Remove redundant initialization of struct ioc_gq"
> Drop "blk-iocost: Get ioc_now inside weight_updated"
> ---
>
> Kemeng Shi (5):
> blk-iocost: Fix typo in comment
> blk-iocost: Reset vtime_base_rate in ioc_refresh_params
> blk-iocost: Trace vtime_base_rate instead of vtime_rate
> blk-iocost: Remove vrate member in struct ioc_now
> blk-iocost: Correct comment in blk_iocost_init
>
> block/blk-iocost.c | 16 +++++++++-------
> include/trace/events/iocost.h | 4 ++--
> 2 files changed, 11 insertions(+), 9 deletions(-)
>
--
Best wishes
Kemeng Shi
next prev parent reply other threads:[~2022-11-23 6:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 12:19 Kemeng Shi
2022-10-18 12:19 ` [PATCH v2 1/5] blk-iocost: Fix typo in comment Kemeng Shi
2022-10-18 12:19 ` [PATCH v2 2/5] blk-iocost: Reset vtime_base_rate in ioc_refresh_params Kemeng Shi
2022-10-18 12:19 ` [PATCH v2 3/5] blk-iocost: Trace vtime_base_rate instead of vtime_rate Kemeng Shi
2022-10-18 12:19 ` [PATCH v2 4/5] blk-iocost: Remove vrate member in struct ioc_now Kemeng Shi
2022-10-18 12:19 ` [PATCH v2 5/5] blk-iocost: Correct comment in blk_iocost_init Kemeng Shi
2022-11-23 6:09 ` Kemeng Shi [this message]
2022-12-01 1:45 ` [PATCH v2 0/5] A few cleanup and bugfix patches for blk-iocost Kemeng Shi
2022-12-01 1:46 ` Jens Axboe
2022-12-01 2:20 ` Kemeng Shi
2022-12-01 2:28 ` Jens Axboe
2022-12-01 1:47 ` Jens Axboe
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=5ae7f0a0-8540-bbfe-2fe7-b18fc071ae1c@huawei.com \
--to=shikemeng@huawei.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®