From: Li Lingfeng <lilingfeng@huaweicloud.com>
To: tj@kernel.org, josef@toxicpanda.com, hch@lst.de, axboe@kernel.dk,
longman@redhat.com, ming.lei@redhat.com
Cc: cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yukuai1@huaweicloud.com,
houtao1@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com,
yukuai3@huawei.com, lilingfeng@huaweicloud.com,
lilingfeng3@huawei.com
Subject: [PATCH v2] blk-cgroup: don't clear stat in blkcg_reset_stats()
Date: Wed, 21 Aug 2024 10:07:56 +0800 [thread overview]
Message-ID: <20240821020756.786000-1-lilingfeng@huaweicloud.com> (raw)
From: Li Lingfeng <lilingfeng3@huawei.com>
The list corruption described in commit 6da668063279 ("blk-cgroup: fix
list corruption from resetting io stat") has no effect. It's unnecessary
to fix it.
As for cgroup v1, it does not use iostat any more after commit
ad7c3b41e86b("blk-throttle: Fix io statistics for cgroup v1"), so using
memset to clear iostat has no real effect.
As for cgroup v2, it will not call blkcg_reset_stats() to corrupt the
list.
The list of root cgroup can be used by both cgroup v1 and v2 while
non-root cgroup can't since it must be removed before switch between
cgroup v1 and v2.
So it may has effect if the list of root used by cgroup v2 was corrupted
after switching to cgroup v1, and switch back to cgroup v2 to use the
corrupted list again.
However, the root cgroup will not use the list any more after commit
ef45fe470e1e("blk-cgroup: show global disk stats in root cgroup io.stat").
Although this has no negative effect, it is not necessary. Remove the
related code for cleanup. No function change.
Signed-off-by: Li Lingfeng <lilingfeng3@huawei.com>
---
v1->v2: remove the fix tag and mark this as cleanup.
block/blk-cgroup.c | 24 ------------------------
1 file changed, 24 deletions(-)
diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
index 69e70964398c..6d091fa55b8c 100644
--- a/block/blk-cgroup.c
+++ b/block/blk-cgroup.c
@@ -629,29 +629,6 @@ static void blkg_iostat_set(struct blkg_iostat *dst, struct blkg_iostat *src)
}
}
-static void __blkg_clear_stat(struct blkg_iostat_set *bis)
-{
- struct blkg_iostat cur = {0};
- unsigned long flags;
-
- flags = u64_stats_update_begin_irqsave(&bis->sync);
- blkg_iostat_set(&bis->cur, &cur);
- blkg_iostat_set(&bis->last, &cur);
- u64_stats_update_end_irqrestore(&bis->sync, flags);
-}
-
-static void blkg_clear_stat(struct blkcg_gq *blkg)
-{
- int cpu;
-
- for_each_possible_cpu(cpu) {
- struct blkg_iostat_set *s = per_cpu_ptr(blkg->iostat_cpu, cpu);
-
- __blkg_clear_stat(s);
- }
- __blkg_clear_stat(&blkg->iostat);
-}
-
static int blkcg_reset_stats(struct cgroup_subsys_state *css,
struct cftype *cftype, u64 val)
{
@@ -668,7 +645,6 @@ static int blkcg_reset_stats(struct cgroup_subsys_state *css,
* anyway. If you get hit by a race, retry.
*/
hlist_for_each_entry(blkg, &blkcg->blkg_list, blkcg_node) {
- blkg_clear_stat(blkg);
for (i = 0; i < BLKCG_MAX_POLS; i++) {
struct blkcg_policy *pol = blkcg_policy[i];
--
2.39.2
next reply other threads:[~2024-08-21 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 2:07 Li Lingfeng [this message]
2024-08-21 15:51 ` Michal Koutný
2024-10-22 3:44 ` Li Lingfeng
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=20240821020756.786000-1-lilingfeng@huaweicloud.com \
--to=lilingfeng@huaweicloud.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=hch@lst.de \
--cc=houtao1@huawei.com \
--cc=josef@toxicpanda.com \
--cc=lilingfeng3@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=ming.lei@redhat.com \
--cc=tj@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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 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®