[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZWRgeAMxQ580-Fgd@tiehlicka>
Date: Mon, 27 Nov 2023 10:25:12 +0100
From: Michal Hocko <mhocko@...e.com>
To: Dmitry Rokosov <ddrokosov@...utedevices.com>
Cc: shakeelb@...gle.com, rostedt@...dmis.org, mhiramat@...nel.org,
hannes@...xchg.org, roman.gushchin@...ux.dev,
muchun.song@...ux.dev, akpm@...ux-foundation.org,
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 2/2] mm: memcg: introduce new event to trace
shrink_memcg
On Thu 23-11-23 14:26:29, Dmitry Rokosov wrote:
> Michal, Shakeel,
>
> Sorry for pinging you here, but I don't quite understand your decision
> on this patchset.
>
> Is it a NAK or not? If it's not, should I consider redesigning
> something? For instance, introducing stub functions to
> remove ifdefs from shrink_node_memcgs().
>
> Thank you for taking the time to look into this!
Sorry for a late reply. I have noticed you have posted a new version.
Let me have a look and comment there.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists