From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] Fix tst_pollute_memory() safety margin for huge systems
Date: Wed, 27 Jan 2021 13:28:35 +0100 [thread overview]
Message-ID: <YBFcc/lc+KkC49Gq@yuki.lan> (raw)
In-Reply-To: <2021012720143348660139@chinatelecom.cn>
Hi!
> According my test,malloc amount greater than available memory,then invoke the oom-killer.
However that does not mean that allocating MemAvailable or slightly less
than MemAvailable is safe. In fact it's not, at least that I've been
told be kernel developers. I will try to figure out something safe
enough with their help.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-01-27 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 11:56 [LTP] [PATCH] Fix tst_pollute_memory() safety margin for huge systems Martin Doucha
2021-01-27 12:03 ` Cyril Hrubis
2021-01-27 12:14 ` liuxp11
2021-01-27 12:28 ` Cyril Hrubis [this message]
2021-01-27 12:30 ` liuxp11
2021-01-27 13:05 ` Li Wang
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=YBFcc/lc+KkC49Gq@yuki.lan \
--to=chrubis@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.