[LTP] [PATCH v1] mmapstress06: Rate limit page-dirtying loop to prevent MemCG OOM-kills

[Andrea Cervesato]

> Thanks for the technical discussion, and we should find better solution
> for avoid oom, but on cgroupv2(does not support disabling the OOM killer)
> scenario, replacing sleep-based pacing with memory.reclaim is simply replacing 
> one guess with another. In user-space, it is impossible to catch the exact 
> second when memory hits memory.max. Furthermore, calling memory.reclaim proactively 
> just guesses when to bypass memory.max altogether, which invalidates the 
> core goal of the test.

Less LLM please :-)

The OOM killer can be disabled in v2, but only for a specific group.

If you don't want to use memory.reclaim in v2 / disable OOM killer in v1,
then we need to do things by hand as explained in the previous comment,
for both v1 and v2.

--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com