Re: [PATCH v3 1/2] mm: vmscan: add cgroup IDs to vmscan tracepoints
From: Shakeel Butt <shakeel.butt@linux.dev>
Date: 2026-01-07 20:35:35
Also in:
linux-mm
From: Shakeel Butt <shakeel.butt@linux.dev>
Date: 2026-01-07 20:35:35
Also in:
linux-mm
On Wed, Jan 07, 2026 at 10:32:08AM -0800, Andrew Morton wrote:
On Wed, 7 Jan 2026 10:14:53 -0800 Shakeel Butt [off-list ref] wrote:quoted
On Mon, Jan 05, 2026 at 02:46:39PM -0800, Shakeel Butt wrote: [...]quoted
Orthogonally I am cleaning up memcg id usage and after that cleanup, mem_cgroup_id() would be preferred way to get the ID. No need to do anything now as I will cleanup this usage later as well.The series has been landed in mm-new. Please use mem_cgroup_id() instead of cgroup_id(memcg->css.cgroup).fyi, I removed this series yesterday due to a CONFIG_MEMCG=n build failure.
Oh sorry, I meant my series [1] landed in mm-new and with that Thomas can directly use mem_cgroup_id() without worrying about CONFIG_MEMCG=n. [1] https://lkml.kernel.org/r/20251225232116.294540-1-shakeel.butt@linux.dev