Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] mmapstress06: Rate limit page-dirtying loop to prevent MemCG OOM-kills
Date: Tue, 25 Aug 2026 03:00:23 +0000	[thread overview]
Message-ID: <20260825030023.9054-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260825022926.9649-1-wegao@suse.com>

Hi Wei,

On Tue, Aug 25, 2026, Wei Gao wrote:
> mmapstress06: Rate limit page-dirtying loop to prevent MemCG OOM-kills

> +		/*
> +		 * Yield periodically to space out allocation spikes and allow
> +		 * asynchronous swap writeback to catch up on slower VM disks.
> +		 */
>  		for (size_t i = 0; i < map_size; i += page_size) {
>  			mmapaddr[i] = 'a';
> -			if ((i % (2 * 1024 * 1024)) == 0)
> -				usleep(1000);
> +			if ((i % (64 * 1024)) == 0)
> +				usleep(200);

Could this avoid using a fixed sleep to synchronize with asynchronous swap
writeback? The 7.2 cgroup documentation says memory.max invokes the cgroup OOM
killer when reclaim cannot reduce usage, while the delay here is unrelated to
actual reclaim progress. A swap device slower than the chosen dirtying rate
can therefore still OOM-kill the child and make the test fail for
environmental timing reasons. Please use reclaim throttling or poll observable
progress with backoff instead of tuning a fixed delay.

Verdict - Needs revision

---
Note:

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-08-25  3:00 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 ` linuxtestproject.agent [this message]
2026-08-25 12:16 ` 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
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=20260825030023.9054-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --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