From: Shakeel Butt <shakeelb@google.com>
To: Dmitry Rokosov <ddrokosov@salutedevices.com>
Cc: rostedt@goodmis.org, mhiramat@kernel.org, hannes@cmpxchg.org,
mhocko@kernel.org, roman.gushchin@linux.dev,
muchun.song@linux.dev, mhocko@suse.com,
akpm@linux-foundation.org, kernel@sberdevices.ru,
rockosov@gmail.com, cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v3 1/2] mm: memcg: print out cgroup ino in the memcg tracepoints
Date: Sat, 25 Nov 2023 04:11:07 +0000 [thread overview]
Message-ID: <20231125041107.wgpskqegywpt7l2o@google.com> (raw)
In-Reply-To: <20231123193937.11628-2-ddrokosov@salutedevices.com>
On Thu, Nov 23, 2023 at 10:39:36PM +0300, Dmitry Rokosov wrote:
> Sometimes, it becomes necessary to determine the memcg tracepoint event
> that has occurred. This is particularly relevant in scenarios involving
> a large cgroup hierarchy, where users may wish to trace the process of
> reclamation within a specific cgroup(s) by applying a filter.
>
> The function cgroup_ino() is a useful tool for this purpose.
> To integrate cgroup_ino() into the existing memcg tracepoints, this
> patch introduces a new tracepoint template for the begin() and end()
> events.
>
> Signed-off-by: Dmitry Rokosov <ddrokosov@salutedevices.com>
Acked-by: Shakeel Butt <shakeelb@google.com>
next prev parent reply other threads:[~2023-11-25 4:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 19:39 [PATCH v3 0/2] mm: memcg: improve vmscan tracepoints Dmitry Rokosov
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 [this message]
2023-11-23 19:39 ` [PATCH v3 2/2] mm: memcg: introduce new event to trace shrink_memcg Dmitry Rokosov
2023-11-25 6:36 ` 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=20231125041107.wgpskqegywpt7l2o@google.com \
--to=shakeelb@google.com \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=ddrokosov@salutedevices.com \
--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 \
/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