From: "Michal Koutný via ltp" <ltp@lists.linux.it>
To: Sebastian Chlad <sebastianchlad@gmail.com>
Cc: Sebastian Chlad <sebastian.chlad@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/2] memcg/memcontrol0[34]: Remove protection from the top level group
Date: Wed, 30 Sep 2026 17:04:15 +0200 [thread overview]
Message-ID: <ar0k7LgZQmrtajlZ@localhost.localdomain> (raw)
In-Reply-To: <20260926204459.20699-3-sebastianchlad@gmail.com>
On Sat, Sep 26, 2026 at 10:44:54PM +0200, Sebastian Chlad <sebastianchlad@gmail.com> wrote:
> From: Sebastian Chlad <sebastian.chlad@suse.com>
>
> The memory pressure in both tests comes from A/G hitting the
> memory.max of A, so A is the reclaim root. Protection of the reclaim
> root is ignored by the kernel and the direct children of the root
> (A/B and A/G) use their own memory.min/memory.low as is, see
> page_counter_calculate_protection(). The 50M of memory.min
> (memcontrol03) and memory.low (memcontrol04) set on A thus has no
> effect on what the tests check; it would only protect the whole
> hierarchy against reclaim from outside, which the tests don't need.
>
> The kselftest the tests are ported from dropped it for the same reason
> in kernel commit 6a35919005d4 ("selftests: memcg: remove protection
> from top level memcg"). Do the same and correct the descriptions, as
> the pressure is created in A, not in A/G.
>
> Signed-off-by: Sebastian Chlad <sebastian.chlad@suse.com>
> ---
> testcases/kernel/controllers/memcg/memcontrol03.c | 5 ++---
> testcases/kernel/controllers/memcg/memcontrol04.c | 5 ++---
> 2 files changed, 4 insertions(+), 6 deletions(-)
Yes, this patch is easily tranferred.
Reviewed-by: Michal Koutný <mkoutny@suse.com>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-09-30 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 20:44 [LTP] [PATCH 0/2] memcg/memcontrol0[34]: Align with the kselftest protection model Sebastian Chlad
2026-09-26 20:44 ` [LTP] [PATCH 1/2] memcg/memcontrol0[34]: Use expected values from the " Sebastian Chlad
2026-09-28 6:27 ` Wei Gao via ltp
2026-09-29 7:06 ` [LTP] " linuxtestproject.agent
2026-09-30 15:04 ` [LTP] [PATCH 1/2] " Michal Koutný via ltp
2026-09-26 20:44 ` [LTP] [PATCH 2/2] memcg/memcontrol0[34]: Remove protection from the top level group Sebastian Chlad
2026-09-28 6:31 ` Wei Gao via ltp
2026-09-30 15:04 ` Michal Koutný via ltp [this message]
2026-09-30 18:36 ` [LTP] [PATCH 0/2] memcg/memcontrol0[34]: Align with the kselftest protection model Cyril Hrubis
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=ar0k7LgZQmrtajlZ@localhost.localdomain \
--to=ltp@lists.linux.it \
--cc=mkoutny@suse.com \
--cc=sebastian.chlad@suse.com \
--cc=sebastianchlad@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.