From: Cyril Hrubis <chrubis@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] mem/min_free_kbytes: Add grace period for memory reclaim
Date: Wed, 27 May 2026 17:40:39 +0200 [thread overview]
Message-ID: <ahcQd-5ffiCDU8IE@yuki.lan> (raw)
In-Reply-To: <20260527050843.14963-1-wegao@suse.com>
Hi!
> High memory pressure can cause MemFree to temporarily drop below the
> min_free_kbytes threshold before the kernel reclaimer can catch up.
> This results in intermittent test failures, particularly observed on
> openQA aarch64 machines.
>
> Implement a 1-second grace period with exponential backoff polling
> (from 1ms up to 512ms) in check_monitor() to allow the kernel time to
> reclaim memory.
>
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Signed-off-by: Wei Gao <wegao@suse.com>
> ---
> v1->v2:
> - Combine TINFO and TFAIL messages in check_monitor() for cleaner output.
> - Remove end = 0;
>
> .../kernel/mem/tunable/min_free_kbytes.c | 33 +++++++++++++------
> 1 file changed, 23 insertions(+), 10 deletions(-)
>
> diff --git a/testcases/kernel/mem/tunable/min_free_kbytes.c b/testcases/kernel/mem/tunable/min_free_kbytes.c
> index a62e4ae9d..e0342ef06 100644
> --- a/testcases/kernel/mem/tunable/min_free_kbytes.c
> +++ b/testcases/kernel/mem/tunable/min_free_kbytes.c
> @@ -1,6 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0-or-later
> /*
> - * Copyright (c) Linux Test Project, 2012-2025
> + * Copyright (c) Linux Test Project, 2012-2026
> * Copyright (C) 2012-2017 Red Hat, Inc.
> */
>
> @@ -140,14 +140,13 @@ static void test_tune(unsigned long overcommit_policy)
> } else {
> if (WIFEXITED(status)) {
> if (WEXITSTATUS(status) != 0) {
> - tst_res(TFAIL, "child unexpectedly "
> - "failed: %d", status);
> + tst_res(TFAIL, "child unexpectedly failed: %d",
> + status);
We do have tst_strstatus().
> }
> } else if (!WIFSIGNALED(status) ||
> WTERMSIG(status) != SIGKILL) {
> - tst_res(TFAIL,
> - "child unexpectedly failed: %d",
> - status);
> + tst_res(TFAIL, "child unexpectedly failed: %d",
> + status);
> }
> }
> }
> @@ -183,18 +182,32 @@ static void check_monitor(void)
> {
> unsigned long tune;
> unsigned long memfree;
> + int i;
>
> while (!end) {
> memfree = SAFE_READ_MEMINFO("MemFree:");
> tune = TST_SYS_CONF_LONG_GET(MIN_FREE_KBYTES);
>
> if (memfree < tune) {
> - tst_res(TINFO, "MemFree is %lu kB, "
> - "min_free_kbytes is %lu kB", memfree, tune);
> - tst_res(TFAIL, "MemFree < min_free_kbytes");
> + /*
> + * Give it some time to reclaim. The kernel should keep
> + * MemFree above min_free_kbytes, but transient drops
> + * are possible under high pressure.
> + */
> + for (i = 1; i < 1024; i *= 2) {
> + usleep(i * 1000);
> + memfree = SAFE_READ_MEMINFO("MemFree:");
> + if (memfree >= tune)
> + break;
> + }
> +
> + if (memfree < tune) {
> + tst_res(TFAIL, "MemFree %lu kB < min_free_kbytes %lu kB",
> + memfree, tune);
> + }
> }
Looks good.
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
I think that we also want to change the test so that the monitor is
started and stopped for each testcase with a specific value we set the
min_free_kbytes to. Running it asynchronously like this may mean that we
will be looking for a wrong value for the second if we are unlucky. But
that can be done later on.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-27 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 5:08 [LTP] [PATCH v2] mem/min_free_kbytes: Add grace period for memory reclaim Wei Gao via ltp
2026-05-27 5:31 ` [LTP] " linuxtestproject.agent
2026-05-27 15:40 ` Cyril Hrubis [this message]
2026-05-29 16:07 ` [LTP] [PATCH v2] " Petr Vorel
2026-05-31 13:51 ` Wei Gao via ltp
2026-05-31 13:40 ` [LTP] [PATCH v3] min_free_kbytes: Handle transient memory drops in check_monitor Wei Gao via ltp
2026-06-01 6:42 ` [LTP] " linuxtestproject.agent
2026-06-02 1:00 ` [LTP] [PATCH v4] " Wei Gao via ltp
2026-06-02 4:02 ` [LTP] " linuxtestproject.agent
2026-06-02 7:46 ` Wei Gao via ltp
2026-06-02 16:07 ` Andrea Cervesato via ltp
2026-06-03 3:07 ` Wei Gao via ltp
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=ahcQd-5ffiCDU8IE@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=wegao@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox