From: Hao Jia <jiahao.os@bytedance.com>
To: Tejun Heo <tj@kernel.org>
Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org, mkoutny@suse.com,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH] cgroup/rstat: record the cumulative per-cpu time of cgroup and its descendants
Date: Thu, 27 Jul 2023 20:05:44 +0800 [thread overview]
Message-ID: <3d2b68bf-9f40-c779-dcfd-4cf9939edecc@bytedance.com> (raw)
In-Reply-To: <b4424767-dce7-08a9-3759-43cc9dfa4273@bytedance.com>
On 2023/7/19 Hao Jia wrote:
>
>
> On 2023/7/19 Tejun Heo wrote:
>> On Tue, Jul 18, 2023 at 06:08:50PM +0800, Hao Jia wrote:
>>> https://github.com/jiaozhouxiaojia/cgv2-stat-percpu_test/tree/main
>>
>> So, we run `stress -c 1` for 1 second in the asdf/test0 cgroup and
>> asdf/cpu.stat correctly reports the cumulative usage. After removing
>> asdf/test0 cgroup, asdf's usage_usec is still there. What's missing here?
>
> Sorry, some of my expressions may have misled you.
>
> Yes, cpu.stat will display the cumulative **global** cpu time of the
> cgroup and its descendants (the corresponding kernel variable is
> "cgrp->bstat"), and it will not be lost when the child cgroup is removed.
>
> Similarly, we need a **per-cpu** variable to record the accumulated
> per-cpu time of cgroup and its descendants.
> The existing kernel variable "cgroup_rstat_cpu(cgrp, cpu)->bstat" is not
> satisfied, it only records the per-cpu time of cgroup itself,
> So I try to add "cgroup_rstat_cpu(cgrp, cpu)->cumul_bstat" to record
> per-cpu time of cgroup and its descendants.
>
> In order to verify the correctness of my patch, I wrote a kernel module
> to compare the results of calculating the per-cpu time of cgroup and its
> descendants in two ways:
> Method 1. Traverse and add the per-cpu rstatc->bstat of cgroup and
> each of its descendants.
> Method 2. Directly read "cgroup_rstat_cpu(cgrp, cpu)->cumul_bstat" in
> the kernel.
>
> When the child cgroup is not removed, the results calculated by the two
> methods should be equal.
>
>> What are you adding?
> I want to add a **per-cpu variable** to record the cumulative per-cpu
> time of cgroup and its descendants, which is similar to the variable
> "cgrp->bstat", but it is a per-cpu variable.
> It is very useful and convenient for calculating the usage of cgroup on
> each cpu, and its behavior is similar to the "cpuacct.usage*" interface
> of cgroup v1.
>
Hello Tejun,
I don't know if I explained it clearly, and do you understand what I mean?
Would you mind adding a variable like this to facilitate per-cpu usage
calculations and migration from cgroup v1 to cgroup v2?
Thanks,
Hao
next prev parent reply other threads:[~2023-07-27 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 9:36 Hao Jia
2023-07-17 19:52 ` Tejun Heo
2023-07-18 10:08 ` [External] " Hao Jia
2023-07-18 21:53 ` Tejun Heo
2023-07-19 3:01 ` Hao Jia
2023-07-27 12:05 ` Hao Jia [this message]
2023-07-27 17:44 ` Tejun Heo
2023-08-02 21:39 ` Tejun Heo
2023-08-07 3:36 ` Hao Jia
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=3d2b68bf-9f40-c779-dcfd-4cf9939edecc@bytedance.com \
--to=jiahao.os@bytedance.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mkoutny@suse.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®