From: Shakeel Butt <shakeel.butt@linux.dev>
To: Thomas Ballasi <tballasi@linux.microsoft.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-trace-kernel@vger.kernel.org, mhiramat@kernel.org,
rostedt@goodmis.org
Subject: Re: [PATCH v5 2/3] mm: vmscan: add cgroup IDs to vmscan tracepoints
Date: Tue, 27 Jan 2026 15:43:48 -0800 [thread overview]
Message-ID: <aXlM7KqRIkerP8Pa@linux.dev> (raw)
In-Reply-To: <20260122182510.2126-3-tballasi@linux.microsoft.com>
On Thu, Jan 22, 2026 at 10:25:09AM -0800, Thomas Ballasi wrote:
> Memory reclaim events are currently difficult to attribute to
> specific cgroups, making debugging memory pressure issues
> challenging. This patch adds memory cgroup ID (memcg_id) to key
> vmscan tracepoints to enable better correlation and analysis.
>
> For operations not associated with a specific cgroup, the field
> is defaulted to 0.
>
> Signed-off-by: Thomas Ballasi <tballasi@linux.microsoft.com>
> ---
> include/trace/events/vmscan.h | 83 ++++++++++++++++++++---------------
> mm/shrinker.c | 6 ++-
> mm/vmscan.c | 17 +++----
> 3 files changed, 61 insertions(+), 45 deletions(-)
>
> diff --git a/include/trace/events/vmscan.h b/include/trace/events/vmscan.h
> index 490958fa10dee..20160e79eb0d7 100644
> --- a/include/trace/events/vmscan.h
> +++ b/include/trace/events/vmscan.h
> @@ -114,85 +114,92 @@ TRACE_EVENT(mm_vmscan_wakeup_kswapd,
>
> DECLARE_EVENT_CLASS(mm_vmscan_direct_reclaim_begin_template,
>
> - TP_PROTO(int order, gfp_t gfp_flags),
> + TP_PROTO(gfp_t gfp_flags, int order, u64 memcg_id),
>
> - TP_ARGS(order, gfp_flags),
> + TP_ARGS(gfp_flags, order, memcg_id),
>
> TP_STRUCT__entry(
> - __field( int, order )
> __field( unsigned long, gfp_flags )
> + __field( u64, memcg_id )
> + __field( int, order )
> ),
>
> TP_fast_assign(
> - __entry->order = order;
> __entry->gfp_flags = (__force unsigned long)gfp_flags;
> + __entry->order = order;
> + __entry->memcg_id = memcg_id;
Please pass memcg pointer to tracepoints and call mem_cgroup_id(memcg)
here.
next prev parent reply other threads:[~2026-01-27 23:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 18:14 [PATCH 0/2] mm: vmscan: add PID and cgroup ID " Thomas Ballasi
2025-12-08 18:14 ` [PATCH 1/2] mm: vmscan: add cgroup IDs " Thomas Ballasi
2025-12-08 18:14 ` [PATCH 2/2] mm: vmscan: add PIDs " Thomas Ballasi
2025-12-10 3:09 ` Steven Rostedt
2025-12-16 14:02 ` [PATCH v2 0/2] mm: vmscan: add PID and cgroup ID " Thomas Ballasi
2025-12-16 14:02 ` [PATCH v2 1/2] mm: vmscan: add cgroup IDs " Thomas Ballasi
2025-12-16 18:50 ` Shakeel Butt
2025-12-17 22:21 ` Steven Rostedt
2025-12-16 14:02 ` [PATCH v2 2/2] mm: vmscan: add PIDs " Thomas Ballasi
2025-12-16 18:03 ` Steven Rostedt
2025-12-29 10:54 ` Thomas Ballasi
2025-12-29 18:29 ` Steven Rostedt
2025-12-29 21:36 ` Steven Rostedt
2026-01-05 16:04 ` [PATCH v3 0/2] mm: vmscan: add PID and cgroup ID " Thomas Ballasi
2026-01-05 16:04 ` [PATCH v3 1/2] mm: vmscan: add cgroup IDs " Thomas Ballasi
2026-01-05 22:46 ` Shakeel Butt
2026-01-07 18:14 ` Shakeel Butt
2026-01-07 18:32 ` Andrew Morton
2026-01-07 20:35 ` Shakeel Butt
2026-01-07 1:56 ` build error on CONFIG_MEMCG=n "error: invalid use of undefined type 'struct mem_cgroup'" Harry Yoo
2026-01-07 2:17 ` Andrew Morton
2026-01-05 16:04 ` [PATCH v3 2/2] mm: vmscan: add PIDs to vmscan tracepoints Thomas Ballasi
2026-01-06 2:06 ` [PATCH v3 0/2] mm: vmscan: add PID and cgroup ID " Andrew Morton
2026-01-06 2:21 ` Steven Rostedt
2026-01-15 12:38 ` [PATCH v4 0/3] " Thomas Ballasi
2026-01-15 12:38 ` [PATCH v4 1/3] tracing: Add __event_in_*irq() helpers Thomas Ballasi
2026-01-15 12:38 ` [PATCH v4 2/3] mm: vmscan: add cgroup IDs to vmscan tracepoints Thomas Ballasi
2026-01-15 12:38 ` [PATCH v4 3/3] mm: vmscan: add PIDs " Thomas Ballasi
2026-01-22 18:25 ` [PATCH v5 0/3] mm: vmscan: add PID and cgroup ID " Thomas Ballasi
2026-01-22 18:25 ` [PATCH v5 1/3] tracing: Add __event_in_*irq() helpers Thomas Ballasi
2026-01-22 18:25 ` [PATCH v5 2/3] mm: vmscan: add cgroup IDs to vmscan tracepoints Thomas Ballasi
2026-01-27 23:43 ` Shakeel Butt [this message]
2026-01-22 18:25 ` [PATCH v5 3/3] mm: vmscan: add PIDs " Thomas Ballasi
2026-01-22 18:52 ` [PATCH v5 0/3] mm: vmscan: add PID and cgroup ID " Andrew Morton
2026-02-13 18:15 ` [PATCH v6 " Thomas Ballasi
2026-02-13 18:15 ` [PATCH v6 1/3] tracing: Add __event_in_*irq() helpers Thomas Ballasi
2026-02-16 16:13 ` Usama Arif
2026-02-17 0:54 ` Steven Rostedt
2026-02-13 18:15 ` [PATCH v6 2/3] mm: vmscan: add cgroup IDs to vmscan tracepoints Thomas Ballasi
2026-02-13 18:15 ` [PATCH v6 3/3] mm: vmscan: add PIDs " Thomas Ballasi
2026-02-16 16:02 ` Usama Arif
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=aXlM7KqRIkerP8Pa@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tballasi@linux.microsoft.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