[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250411152856.41a12ac2b3eb1005a86168e6@linux-foundation.org>
Date: Fri, 11 Apr 2025 15:28:56 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Waiman Long <llong@...hat.com>
Cc: Michal Koutný <mkoutny@...e.com>, Johannes Weiner
<hannes@...xchg.org>, Michal Hocko <mhocko@...nel.org>, Roman Gushchin
<roman.gushchin@...ux.dev>, Shakeel Butt <shakeel.butt@...ux.dev>, Muchun
Song <muchun.song@...ux.dev>, Tejun Heo <tj@...nel.org>, Shuah Khan
<shuah@...nel.org>, linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
linux-mm@...ck.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v4 1/2] mm/vmscan: Skip memcg with !usage in
shrink_node_memcgs()
On Fri, 11 Apr 2025 17:08:33 -0400 Waiman Long <llong@...hat.com> wrote:
> > - * A/B/F memory.current = 0
> > + * A/B/C memory.current ~= 29M, memory.events:low > 0
> > + * A/B/D memory.current ~= 21M, memory.events:low > 0
> > + * A/B/E memory.current ~= 0, memory.events:low not specified (==0 w/out memory_recursiveprot)
> > + * A/B/F memory.current = 0, memory.events:low == 0
> > * (for origin of the numbers, see model in memcg_protection.m.)
>
> Sorry for the late reply. I think it is a good idea to update the header
> as well. This function is actually used by both test_memcg_low and
> test_memcg.min. So I will use low/min instead.
It appears that quite a few updates are expected for this series,
so I'll drop v4 from mm.git.
Powered by blists - more mailing lists