From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] min_free_kbytes: TCONF on errno ENOMEM, add break
Date: Mon, 25 May 2026 13:15:06 +0200 [thread overview]
Message-ID: <ahQvOj1-I9f7Y8OS@yuki.lan> (raw)
In-Reply-To: <20260525094224.GA181471@pevik>
Hi!
> > This looks suspicious. If we fail with the fork here that probably means
> > that the memory allocated by the previous iteration wasn't reclaimed
> > fast enough. Was this on a second or third iteration (we do three
> > iterations with different overcommit values)?
>
> This is on one of my bare metal machines, first iteration:
>
> min_free_kbytes.c:91: TINFO: Setting /proc/sys/vm/overcommit_memory to 2
> min_free_kbytes.c:95: TINFO: Setting /proc/sys/vm/min_free_kbytes to 67584
> min_free_kbytes.c:111: TBROK: fork: ENOMEM (12)
> tst_test.c:1933: TINFO: Killed the leftover descendant processes
With overcommit = 2 (never) this just means that memory on your machine
has been all consumed[1]. It may make sense to TCONF on overcommit=2 but
I'm not so sure the other two overcommit modes.
[1] The available memory is counted as swap + 50% of RAM
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-25 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 7:39 [LTP] [PATCH 1/1] min_free_kbytes: TCONF on errno ENOMEM, add break Petr Vorel
2026-05-25 9:02 ` Cyril Hrubis
2026-05-25 9:42 ` Petr Vorel
2026-05-25 11:15 ` Cyril Hrubis [this message]
2026-05-25 11:36 ` Petr Vorel
2026-05-25 10:08 ` [LTP] " linuxtestproject.agent
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=ahQvOj1-I9f7Y8OS@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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