From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitry Rokosov <ddrokosov@salutedevices.com>
Cc: <hannes@cmpxchg.org>, <mhocko@kernel.org>,
<roman.gushchin@linux.dev>, <shakeelb@google.com>,
<muchun.song@linux.dev>, <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 v2 0/3] samples: introduce cgroup events listeners
Date: Fri, 10 Nov 2023 08:59:52 -0800 [thread overview]
Message-ID: <20231110085952.b55345df8dd18019f0581fc1@linux-foundation.org> (raw)
In-Reply-To: <20231110082045.19407-1-ddrokosov@salutedevices.com>
On Fri, 10 Nov 2023 11:20:42 +0300 Dmitry Rokosov <ddrokosov@salutedevices.com> wrote:
> To begin with, this patch series relocates the cgroup example code to
> the samples/cgroup directory, which is the appropriate location for such
> code snippets.
>
> Furthermore, a new cgroup v2 events listener is introduced. This
> listener is a simple yet effective tool for monitoring memory events and
> managing counter changes during runtime.
Is this correctly named? It's a memcg event listener.
"cgroup_v2_event_listener" implies that it will display events for
other/all cgroup v2 controllers.
next prev parent reply other threads:[~2023-11-10 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 8:20 Dmitry Rokosov
2023-11-10 8:20 ` [PATCH v2 1/3] samples: introduce new samples subdir for cgroup Dmitry Rokosov
2023-11-10 8:20 ` [PATCH v2 2/3] samples/cgroup: introduce cgroup v2 memory.events listener Dmitry Rokosov
2023-11-10 8:20 ` [PATCH v2 3/3] mm: memcg: add reminder comment for the memcg v2 events Dmitry Rokosov
2023-11-10 16:59 ` Andrew Morton [this message]
2023-11-11 13:39 ` [PATCH v2 0/3] samples: introduce cgroup events listeners 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=20231110085952.b55345df8dd18019f0581fc1@linux-foundation.org \
--to=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=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=rockosov@gmail.com \
--cc=roman.gushchin@linux.dev \
--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