From: Tejun Heo <tj@kernel.org>
To: Hao Jia <jiahao.os@bytedance.com>
Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org, mkoutny@suse.com,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup/rstat: record the cumulative per-cpu time of cgroup and its descendants
Date: Mon, 17 Jul 2023 09:52:24 -1000 [thread overview]
Message-ID: <ZLWb-LsBD041hMvr@slm.duckdns.org> (raw)
In-Reply-To: <20230717093612.40846-1-jiahao.os@bytedance.com>
Hello,
On Mon, Jul 17, 2023 at 05:36:12PM +0800, Hao Jia wrote:
> Now the member variable bstat of the structure cgroup_rstat_cpu
You said "now" indicating that the behavior has changed recently but I don't
see what changed there. Can you elaborate?
> records the per-cpu time of the cgroup itself, but does not
> include the per-cpu time of its descendants. The per-cpu time
It does. The per-cpu delta is added to its parent and then that will in turn
be used to propagate to its parent.
> including descendants is very useful for calculating the
> per-cpu usage of cgroups.
>
> Although we can indirectly obtain the total per-cpu time
> of the cgroup and its descendants by accumulating the per-cpu
> bstat of each descendant of the cgroup. But after a child cgroup
> is removed, we will lose its bstat information. This will cause
> the cumulative value to be non-monotonic, thus affecting
> the accuracy of cgroup per-cpu usage.
>
> So we add the cumul_bstat variable to record the total
> per-cpu time of this cgroup and its descendants, which is
> similar to "cpuacct.usage*" in cgroup v1. And this is
> also helpful for the migration from cgroup v1 to cgroup v2.
> After adding this variable, we can obtain the per-cpu time of
> cgroup and its descendants in user mode through eBPF, etc.
I think you're misunderstanding how the code works. Can you please double
check?
Thanks.
--
tejun
next prev parent reply other threads:[~2023-07-17 19:52 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 [this message]
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
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=ZLWb-LsBD041hMvr@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jiahao.os@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mkoutny@suse.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®