[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231127113739.djqzy2p2ofstjmm3@CAB-WSD-L081021>
Date: Mon, 27 Nov 2023 14:37:39 +0300
From: Dmitry Rokosov <ddrokosov@...utedevices.com>
To: Michal Hocko <mhocko@...e.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
Michal,
On Mon, Nov 27, 2023 at 10:25:12AM +0100, Michal Hocko wrote:
> 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.
No problem! Thanks a lot for your time and attention! Let's continue in
the next version thread.
--
Thank you,
Dmitry
Powered by blists - more mailing lists