From: Martin Doucha <mdoucha@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lib: memutils: don't pollute entire system memory to avoid OoM
Date: Thu, 24 Jun 2021 15:33:10 +0200 [thread overview]
Message-ID: <018a369f-473b-524d-f81b-eb8be4df49bb@suse.cz> (raw)
In-Reply-To: <20210624132226.84611-1-krzysztof.kozlowski@canonical.com>
On 24. 06. 21 15:22, Krzysztof Kozlowski wrote:
> On big memory systems, e.g. 196 GB RAM machine, the ioctl_sg01 test was
> failing because of OoM killer during memory pollution:
>
> ...
>
> It seems leaving hard-coded 128 MB free memory works for small or medium
> systems, but for such bigger machine it creates significant memory
> pressure triggering the out of memory reaper.
>
> The memory pressure usually is defined by ratio between free and total
> memory, so adjust the safety/spare memory similarly to keep always 0.5%
> of memory free.
Hi,
I've sent a similar patch for the same issue a while ago. It covers a
few more edge cases. See [1] for the discussion about it.
[1]
https://patchwork.ozlabs.org/project/ltp/patch/20210127115606.28985-1-mdoucha@suse.cz/
--
Martin Doucha mdoucha@suse.cz
QA Engineer for Software Maintenance
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic
next prev parent reply other threads:[~2021-06-24 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 13:22 [LTP] [PATCH] lib: memutils: don't pollute entire system memory to avoid OoM Krzysztof Kozlowski
2021-06-24 13:33 ` Martin Doucha [this message]
2021-06-24 14:00 ` Li Wang
2021-06-24 14:13 ` Martin Doucha
2021-06-24 15:07 ` Krzysztof Kozlowski
2021-06-24 15:34 ` Krzysztof Kozlowski
2021-06-24 15:46 ` Krzysztof Kozlowski
2021-09-08 13:37 ` Cyril Hrubis
2021-09-08 13:37 ` Cyril Hrubis
2021-09-08 13:54 ` Martin Doucha
2021-09-08 13:54 ` Martin Doucha
2021-09-08 14:17 ` Cyril Hrubis
2021-09-08 14:17 ` Cyril Hrubis
2021-09-08 14:19 ` Krzysztof Kozlowski
2021-09-08 14:19 ` Krzysztof Kozlowski
2021-09-08 14:32 ` Cyril Hrubis
2021-09-08 14:32 ` Cyril Hrubis
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=018a369f-473b-524d-f81b-eb8be4df49bb@suse.cz \
--to=mdoucha@suse.cz \
--cc=ltp@lists.linux.it \
/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.