[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231124200633.scnct5f7auawsjn2@CAB-WSD-L081021>
Date: Fri, 24 Nov 2023 23:06:33 +0300
From: Dmitry Rokosov <ddrokosov@...utedevices.com>
To: Andrew Morton <akpm@...ux-foundation.org>
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 v3 0/3] samples: introduce cgroup events listeners
On Fri, Nov 24, 2023 at 11:42:30AM -0800, Andrew Morton wrote:
> On Thu, 23 Nov 2023 10:19: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.
>
> butbut. Didn't we decide to do s/cgroup/memcg/ throughout?
I believe the samples directory should be named "samples/cgroup" instead
of "memcg" because the cgroup v1 event listener cannot be renamed to
"memcg" due to the common naming of cgroup v1 event_control (this sample
uses that control to access eventfd).
Additionally, I think it would be a good idea to add the new samples for
cgroup helpers in that directory.
That's why I have only renamed the new memcg listener.
--
Thank you,
Dmitry
Powered by blists - more mailing lists