[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231101102837.25205-1-ddrokosov@salutedevices.com>
Date: Wed, 1 Nov 2023 13:28:35 +0300
From: Dmitry Rokosov <ddrokosov@...utedevices.com>
To: <rostedt@...dmis.org>, <mhiramat@...nel.org>, <hannes@...xchg.org>,
<mhocko@...nel.org>, <roman.gushchin@...ux.dev>,
<shakeelb@...gle.com>, <muchun.song@...ux.dev>,
<akpm@...ux-foundation.org>
CC: <kernel@...rdevices.ru>, <rockosov@...il.com>,
<cgroups@...r.kernel.org>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, <bpf@...r.kernel.org>,
Dmitry Rokosov <ddrokosov@...rdevices.ru>
Subject: [PATCH v1 0/2] mm: memcg: improve vmscan tracepoints
From: Dmitry Rokosov <ddrokosov@...rdevices.ru>
The motivation behind this commit is to enhance the traceability and
understanding of memcg events. By integrating the function cgroup_name()
into the existing memcg tracepoints, this patch series introduces a new
tracepoint template for the begin() and end() events. It utilizes a
static __array() to store the cgroup name, enabling developers to easily
identify the cgroup associated with a specific memcg tracepoint event.
Additionally, this patch series introduces new shrink_memcg tracepoints
to facilitate non-direct memcg reclaim tracing and debugging.
Dmitry Rokosov (2):
mm: memcg: print out cgroup name in the memcg tracepoints
mm: memcg: introduce new event to trace shrink_memcg
include/trace/events/vmscan.h | 91 ++++++++++++++++++++++++++++++-----
mm/vmscan.c | 15 ++++--
2 files changed, 90 insertions(+), 16 deletions(-)
--
2.25.1
Powered by blists - more mailing lists