From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Wei Gao" <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] mmapstress06: Rate limit page-dirtying loop to prevent MemCG OOM-kills
Date: Thu, 27 Aug 2026 08:06:31 +0000 [thread overview]
Message-ID: <6a8ff007.b1f9e4c6.15919c.5636@mx.google.com> (raw)
In-Reply-To: <ao7sDiRA4JguwRUl@autotest-wegao.qe.prg2.suse.org>
> I guess "need to do things by hand" includes totally removing the hard
> sleep time; currently, I have no good solution (as I mentioned in previous
> comments, memory.reclaim is not an option).
yes, basically we re-implement some sort of OOM-killer/memory.reclaim
inside the code, instead of using them directly. That means we need to
disable OOM killer, loop over the current swap status and eventually
raise an error if after N iterations pages are not swapped.
But I feel it's not deterministic because on a really slow device we
might run out of iterations. I still think memory.reclaim is the best
choice for v2 in this case, because it will wait until a certain amount
of memory has been reclaimed and eventually raise an error.
@Cyril do you have any idea on how to proceed here?
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-27 8:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 2:13 [LTP] [PATCH v1] mmapstress06: Rate limit page-dirtying loop to prevent MemCG OOM-kills Wei Gao via ltp
2026-08-25 3:00 ` [LTP] " linuxtestproject.agent
2026-08-25 12:16 ` [LTP] [PATCH v1] " Andrea Cervesato via ltp
2026-08-26 7:13 ` Wei Gao via ltp
2026-08-26 7:58 ` Andrea Cervesato via ltp
2026-08-26 9:31 ` Wei Gao via ltp
2026-08-26 9:49 ` Andrea Cervesato via ltp
2026-08-26 13:38 ` Wei Gao via ltp
2026-08-27 8:06 ` Andrea Cervesato via ltp [this message]
2026-08-27 14:21 ` Cyril Hrubis
2026-09-01 2:04 ` Wei Gao via ltp
2026-09-01 7:38 ` Andrea Cervesato via ltp
2026-09-01 8:22 ` Wei Gao via ltp
2026-09-01 8:47 ` Cyril Hrubis
2026-09-02 2:57 ` [LTP] [PATCH v2] mmapstress06: Use memory.high in cgroup v2 to start swapping early Wei Gao via ltp
2026-09-02 8:28 ` [LTP] " linuxtestproject.agent
2026-09-04 8:53 ` [LTP] [PATCH v2] " Andrea Cervesato via ltp
2026-09-04 10:23 ` Cyril Hrubis
2026-09-04 10:43 ` Andrea Cervesato 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=6a8ff007.b1f9e4c6.15919c.5636@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--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 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.