From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] mem/lib: keep allocating memory until get an error in single process
Date: Tue, 21 Jun 2016 11:26:17 +0800 [thread overview]
Message-ID: <20160621031245.GA24636@gmail.com> (raw)
In-Reply-To: <214135224.352328.1466427831586.JavaMail.zimbra@redhat.com>
On Mon, Jun 20, 2016 at 09:03:51AM -0400, Jan Stancek wrote:
> >
> > 2. The child_alloc() probably should also do memory allocation with an
> > infinite loop
>
> At the time 'lite' was introduced, everything was single threaded,
> the only difference was that lite == 0 would keep allocating in
> infinite loop.
>
> Your patch is effectively eliminating lite == 1, which means that
> oom03 will pass even if cgroup limits are broken.
You're right! My previous meothod didn't solve the essential problem.
>
> > in single process mode. Because if someone has a caller testoom(0, 1, ENOMEM,
> > 1) at other
> > place in future, that'll be easily get fauilures.
>
> Likely because author is expecting behaviour other than what
> we have now:
>
> * @lite: if non-zero, child makes only single TESTMEM+MB allocation
> * if zero, child keeps allocating memory until it gets killed
> * or some operation fails
Okay, now just keep it this way.
>
> > Or, can we solve them in one method?
>
> We could skip oom(KSM) if lite == 1 in testoom(), since limit_in_bytes
> may vary from run to run, which isn't reliable for oom03 cgroup test.
>
> Or we could change alloc_mem for lite == 1 && testcase == KSM,
> such that each page would have unique content (to prevent merging).
Yes, and we clould also keep the KSM scan off while lite == 1.
if (lite != 1) SAFE_FILE_PRINTF(cleanup, PATH_KSM "run", "1");
Let me format a new patch for this.
Regards,
Li WANG
prev parent reply other threads:[~2016-06-21 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 9:53 [LTP] [PATCH] mem/lib: keep allocating memory until get an error in single process Li Wang
2016-06-20 10:43 ` Jan Stancek
2016-06-20 11:34 ` Li Wang
2016-06-20 13:03 ` Jan Stancek
2016-06-21 3:26 ` Li Wang [this message]
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=20160621031245.GA24636@gmail.com \
--to=liwang@redhat.com \
--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