From: Waiman Long <llong@redhat.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v4 1/2] mm/vmscan: Skip memcg with !usage in shrink_node_memcgs()
Date: Fri, 11 Apr 2025 17:08:33 -0400 [thread overview]
Message-ID: <6d81d576-7e94-4523-af9a-d43298ea64ba@redhat.com> (raw)
In-Reply-To: <awgbdn6gwnj4kfaezsorvopgsdyoty3yahdeanqvoxstz2w2ke@xc3sv43elkz5>
On 4/7/25 11:25 AM, Michal Koutný wrote:
> Hi Waiman.
>
> On Sun, Apr 06, 2025 at 09:41:58PM -0400, Waiman Long <longman@redhat.com> wrote:
> ...
>> diff --git a/tools/testing/selftests/cgroup/test_memcontrol.c b/tools/testing/selftests/cgroup/test_memcontrol.c
>> index 16f5d74ae762..bab826b6b7b0 100644
>> --- a/tools/testing/selftests/cgroup/test_memcontrol.c
>> +++ b/tools/testing/selftests/cgroup/test_memcontrol.c
> I'd suggest updating also the header of the test for clarity and then
> exempt the Child 2 ('E') conditionally from comparisons, something like:
>
> @@ -380,10 +380,10 @@ static bool reclaim_until(const char *memcg, long goal);
> *
> * Then it checks actual memory usages and expects that:
> * A/B memory.current ~= 50M
> - * A/B/C memory.current ~= 29M
> - * A/B/D memory.current ~= 21M
> - * A/B/E memory.current ~= 0
> - * 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.
Cheers,
Longman
> *
> * After that it tries to allocate more than there is
> @@ -527,6 +527,7 @@ static int test_memcg_protection(const char *root, bool min)
>
> for (i = 0; i < ARRAY_SIZE(children); i++) {
> int no_low_events_index = 1;
> + int ignore_low_events_index = has_recursiveprot ? 2 : -1;
> long low, oom;
>
> oom = cg_read_key_long(children[i], "memory.events", "oom ");
> @@ -534,6 +535,8 @@ static int test_memcg_protection(const char *root, bool min)
>
> if (oom)
> goto cleanup;
> + if (i == ignore_low_events_index)
> + continue;
> if (i <= no_low_events_index && low <= 0)
> goto cleanup;
> if (i > no_low_events_index && low)
next prev parent reply other threads:[~2025-04-11 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 1:41 [PATCH v4 0/2] memcg: Fix test_memcg_min/low test failures Waiman Long
2025-04-07 1:41 ` [PATCH v4 1/2] mm/vmscan: Skip memcg with !usage in shrink_node_memcgs() Waiman Long
2025-04-07 14:24 ` Johannes Weiner
2025-04-07 14:36 ` Waiman Long
2025-04-07 15:25 ` Michal Koutný
2025-04-11 21:08 ` Waiman Long [this message]
2025-04-11 22:28 ` Andrew Morton
2025-04-07 1:41 ` [PATCH v4 2/2] selftests: memcg: Increase error tolerance of child memory.current check in test_memcg_protection() Waiman Long
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6d81d576-7e94-4523-af9a-d43298ea64ba@redhat.com \
--to=llong@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=shuah@kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox