[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231110085952.b55345df8dd18019f0581fc1@linux-foundation.org>
Date: Fri, 10 Nov 2023 08:59:52 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dmitry Rokosov <ddrokosov@...utedevices.com>
Cc: <hannes@...xchg.org>, <mhocko@...nel.org>,
<roman.gushchin@...ux.dev>, <shakeelb@...gle.com>,
<muchun.song@...ux.dev>, <kernel@...rdevices.ru>,
<rockosov@...il.com>, <cgroups@...r.kernel.org>,
<linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>,
<bpf@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] samples: introduce cgroup events listeners
On Fri, 10 Nov 2023 11:20:42 +0300 Dmitry Rokosov <ddrokosov@...utedevices.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.
Powered by blists - more mailing lists