[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YmM0b+3thMZaXVDb@carbon>
Date: Fri, 22 Apr 2022 16:04:15 -0700
From: Roman Gushchin <roman.gushchin@...ux.dev>
To: David Vernet <void@...ifault.com>
Cc: akpm@...ux-foundation.org, tj@...nel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
cgroups@...r.kernel.org, hannes@...xchg.org, mhocko@...nel.org,
shakeelb@...gle.com, kernel-team@...com
Subject: Re: [PATCH 1/5] cgroups: Refactor children cgroups in memcg tests
On Fri, Apr 22, 2022 at 08:57:25AM -0700, David Vernet wrote:
> In test_memcg_min() and test_memcg_low(), there is an array of four sibling
> cgroups. All but one of these sibling groups does a 50MB allocation, and
> the group that does no allocation is the third of four in the array. This
> is not a problem per se, but makes it a bit tricky to do some assertions in
> test_memcg_low(), as we want to make assertions on the siblings based on
> whether or not they performed allocations. Having a static index before
> which all groups have performed an allocation makes this cleaner.
>
> This patch therefore reorders the sibling groups so that the group that
> performs no allocations is the last in the array.
It makes the comment explaining the test just above the test_memcg_min()
function obsolete. Please, fix it too.
Thanks!
Powered by blists - more mailing lists