From: Dmitry Rokosov <ddrokosov@salutedevices.com>
To: <rostedt@goodmis.org>, <mhiramat@kernel.org>,
<hannes@cmpxchg.org>, <mhocko@kernel.org>,
<roman.gushchin@linux.dev>, <shakeelb@google.com>,
<muchun.song@linux.dev>, <mhocko@suse.com>,
<akpm@linux-foundation.org>
Cc: <kernel@sberdevices.ru>, <rockosov@gmail.com>,
<cgroups@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <bpf@vger.kernel.org>,
Dmitry Rokosov <ddrokosov@salutedevices.com>
Subject: [PATCH v3 0/2] mm: memcg: improve vmscan tracepoints
Date: Thu, 23 Nov 2023 22:39:35 +0300 [thread overview]
Message-ID: <20231123193937.11628-1-ddrokosov@salutedevices.com> (raw)
The motivation behind this commit is to enhance the traceability and
understanding of memcg events. By integrating the function cgroup_ino()
into the existing memcg tracepoints, this patch series introduces a new
tracepoint template for the begin() and end() events. It utilizes a new
entry field ino to store the cgroup ino, 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.
Changes v3 since v2 at [2]:
- use cgroup_ino() instead of cgroup_name() for memcg tracepoints
because cgroup_name() acquires a global rw_lock, which can
potentially slow down the system
- introduce a stub macro for each shrink_memcg tracepoint to avoid
using ifdefs within the common vmscan code."
Changes v2 since v1 at [1]:
- change the position of the "memcg" parameter to ensure backward
compatibility with userspace tools that use memcg tracepoints
- add additional CONFIG_MEMCG ifdefs to prevent the use of memcg
tracepoints when memcg is disabled
Links:
[1] https://lore.kernel.org/all/20231101102837.25205-1-ddrokosov@salutedevices.com/
[2] https://lore.kernel.org/all/20231123071945.25811-1-ddrokosov@salutedevices.com/
Dmitry Rokosov (2):
mm: memcg: print out cgroup ino in the memcg tracepoints
mm: memcg: introduce new event to trace shrink_memcg
include/trace/events/vmscan.h | 95 ++++++++++++++++++++++++++++++-----
mm/vmscan.c | 17 +++++--
2 files changed, 95 insertions(+), 17 deletions(-)
--
2.36.0
next reply other threads:[~2023-11-23 19:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 19:39 Dmitry Rokosov [this message]
2023-11-23 19:39 ` [PATCH v3 1/2] mm: memcg: print out cgroup ino in the memcg tracepoints Dmitry Rokosov
2023-11-25 4:11 ` Shakeel Butt
[not found] ` <20231123193937.11628-3-ddrokosov@salutedevices.com>
2023-11-25 6:36 ` [PATCH v3 2/2] mm: memcg: introduce new event to trace shrink_memcg Shakeel Butt
2023-11-25 8:01 ` Dmitry Rokosov
2023-11-25 17:38 ` Shakeel Butt
2023-11-25 17:47 ` Shakeel Butt
2023-11-27 9:33 ` Michal Hocko
2023-11-27 11:36 ` Dmitry Rokosov
2023-11-27 12:50 ` Michal Hocko
2023-11-27 16:16 ` Dmitry Rokosov
2023-11-28 9:32 ` Michal Hocko
2023-11-29 15:20 ` Dmitry Rokosov
2023-11-29 15:26 ` Dmitry Rokosov
2023-11-29 16:06 ` Michal Hocko
2023-11-29 16:57 ` Dmitry Rokosov
2023-11-29 17:10 ` Michal Hocko
2023-11-29 17:34 ` Steven Rostedt
2023-11-29 17:35 ` Dmitry Rokosov
2023-11-29 17:33 ` Andrew Morton
2023-11-29 17:49 ` Dmitry Rokosov
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=20231123193937.11628-1-ddrokosov@salutedevices.com \
--to=ddrokosov@salutedevices.com \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel@sberdevices.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhiramat@kernel.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=rockosov@gmail.com \
--cc=roman.gushchin@linux.dev \
--cc=rostedt@goodmis.org \
--cc=shakeelb@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