From: Shakeel Butt <shakeel.butt@linux.dev>
To: inwardvessel <inwardvessel@gmail.com>
Cc: tj@kernel.org, yosryahmed@google.com, mhocko@kernel.org,
hannes@cmpxchg.org, akpm@linux-foundation.org,
linux-mm@kvack.org, cgroups@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH 4/4 v2] cgroup: separate rstat list pointers from base stats
Date: Thu, 27 Feb 2025 15:01:27 -0800 [thread overview]
Message-ID: <3asrhag2zfxzlmtjqwzmmuyt5tn57d3se7uvhpuloavsc4dvwa@2my4xmpabl2o> (raw)
In-Reply-To: <20250227215543.49928-5-inwardvessel@gmail.com>
On Thu, Feb 27, 2025 at 01:55:43PM -0800, inwardvessel wrote:
> From: JP Kobryn <inwardvessel@gmail.com>
>
> A majority of the cgroup_rstat_cpu struct size is made up of the base
> stat entities. Since only the "self" subsystem state makes use of these,
> move them into a struct of their own. This allows for a new compact
> cgroup_rstat_cpu struct that the formal subsystems can make use of.
> Where applicable, decide on whether to allocate the compact or full
> struct including the base stats.
>
> Signed-off-by: JP Kobryn <inwardvessel@gmail.com>
One nit below otherwise:
Reviewed-by: Shakeel Butt <shakeel.butt@linux.dev>
[...]
> @@ -438,17 +444,31 @@ int cgroup_rstat_init(struct cgroup_subsys_state *css)
>
> /* the root cgrp's self css has rstat_cpu preallocated */
> if (!css->rstat_cpu) {
Early return here for root to eliminate one indent in this function.
> - css->rstat_cpu = alloc_percpu(struct cgroup_rstat_cpu);
> - if (!css->rstat_cpu)
> - return -ENOMEM;
> - }
> + if (is_base_css(css)) {
> + css->rstat_base_cpu = alloc_percpu(struct cgroup_rstat_base_cpu);
> + if (!css->rstat_base_cpu)
> + return -ENOMEM;
>
> - /* ->updated_children list is self terminated */
> - for_each_possible_cpu(cpu) {
> - struct cgroup_rstat_cpu *rstatc = cgroup_rstat_cpu(css, cpu);
> + for_each_possible_cpu(cpu) {
> + struct cgroup_rstat_base_cpu *rstatc;
> +
> + rstatc = cgroup_rstat_base_cpu(css, cpu);
> + rstatc->self.updated_children = css;
> + u64_stats_init(&rstatc->bsync);
> + }
> + } else {
> + css->rstat_cpu = alloc_percpu(struct cgroup_rstat_cpu);
> + if (!css->rstat_cpu)
> + return -ENOMEM;
> +
> + for_each_possible_cpu(cpu) {
> + struct cgroup_rstat_cpu *rstatc;
> +
> + rstatc = cgroup_rstat_cpu(css, cpu);
> + rstatc->updated_children = css;
> + }
> + }
>
> - rstatc->updated_children = css;
> - u64_stats_init(&rstatc->bsync);
> }
next prev parent reply other threads:[~2025-02-27 23:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 21:55 [PATCH 0/4 v2] cgroup: separate rstat trees inwardvessel
2025-02-27 21:55 ` [PATCH 1/4 v2] cgroup: move cgroup_rstat from cgroup to cgroup_subsys_state inwardvessel
2025-02-27 22:43 ` Shakeel Butt
2025-02-28 19:04 ` Yosry Ahmed
2025-03-01 1:06 ` JP Kobryn
2025-03-01 1:25 ` Yosry Ahmed
2025-03-01 1:30 ` JP Kobryn
2025-03-03 18:18 ` Shakeel Butt
2025-03-03 18:21 ` Yosry Ahmed
2025-03-03 15:20 ` Michal Koutný
2025-03-03 19:31 ` JP Kobryn
2025-02-27 21:55 ` [PATCH 2/4 v2] cgroup: rstat lock indirection inwardvessel
2025-03-03 15:21 ` Michal Koutný
2025-02-27 21:55 ` [PATCH 3/4 v2] cgroup: separate rstat locks for subsystems inwardvessel
2025-02-27 22:52 ` Shakeel Butt
2025-02-28 16:07 ` JP Kobryn
2025-02-28 17:37 ` JP Kobryn
2025-02-28 19:20 ` Yosry Ahmed
2025-03-06 21:47 ` JP Kobryn
2025-03-01 23:00 ` kernel test robot
2025-03-03 15:22 ` Michal Koutný
2025-03-03 18:29 ` Yosry Ahmed
2025-03-03 18:40 ` Shakeel Butt
2025-03-03 19:23 ` JP Kobryn
2025-03-03 19:39 ` Shakeel Butt
2025-03-03 19:50 ` Yosry Ahmed
2025-03-03 20:09 ` Shakeel Butt
2025-03-03 18:49 ` Michal Koutný
2025-03-10 17:59 ` JP Kobryn
2025-03-11 13:49 ` Michal Koutný
2025-03-06 21:36 ` JP Kobryn
2025-03-03 23:49 ` kernel test robot
2025-02-27 21:55 ` [PATCH 4/4 v2] cgroup: separate rstat list pointers from base stats inwardvessel
2025-02-27 23:01 ` Shakeel Butt [this message]
2025-02-28 20:33 ` Yosry Ahmed
2025-02-28 18:22 ` [PATCH 0/4 v2] cgroup: separate rstat trees Yosry Ahmed
2025-03-03 15:19 ` Michal Koutný
2025-03-06 1:07 ` JP Kobryn
2025-03-11 13:49 ` Michal Koutný
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=3asrhag2zfxzlmtjqwzmmuyt5tn57d3se7uvhpuloavsc4dvwa@2my4xmpabl2o \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=inwardvessel@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=tj@kernel.org \
--cc=yosryahmed@google.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