Linux Test Project
 help / color / mirror / Atom feed
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:03:56 +0100	[thread overview]
Message-ID: <YBFWrJoS1tVmWGFx@yuki.lan> (raw)
In-Reply-To: <20210127115606.28985-1-mdoucha@suse.cz>

Hi!
Actually I've been thinking about this one and since this is a strictly
best effort action I think we should be more aggressive about the safety
margin.

I also started to talk to kernel developers about this and generally
about tests that try to allocate maximal amount of memory without
triggering OOM since we have a few in the tree. I will send the results
of this discussion once I have any here as well.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2021-01-27 12:03 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 [this message]
2021-01-27 12:14   ` liuxp11
2021-01-27 12:28     ` Cyril Hrubis
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=YBFWrJoS1tVmWGFx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox