From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] tst_pollute_memory(): Set minimal safety margin to 64MB
Date: Wed, 20 Jan 2021 16:06:41 +0100 [thread overview]
Message-ID: <YAhHAWTedDb/6Hd/@yuki.lan> (raw)
In-Reply-To: <CA+G9fYuDpnJOcHA5Me4KM4v+NaFW=2_3id=Am6skbDavb1iACw@mail.gmail.com>
Hi!
> > > I have applied your patch and rebuilt completely and retested
> > > ioctl_sg01 test case in a loop on three different devices.
> > >
> > > 1 PASS out of 20 runs with overcommit_memory 0 on x86_64.
> > > 1 PASS out of 20 runs with overcommit_memory 1 on x86_64.
> > >
> > > Which means 19 times the test case triggered oom-killer and the test was broken.
> >
> > So it looks like 64MB is not enough in your case.
> >
> > Does it work with 128MB or 256MB?
> >
> > i.e.:
> >
> > safety = MAX(4096 * SAFE_SYSCONF(_SC_PAGESIZE), 128 * 1024 * 1024);
> > safety = MAX(4096 * SAFE_SYSCONF(_SC_PAGESIZE), 256 * 1024 * 1024);
>
>
> I will test with these changes and get back to you.
>
> Meanwhile,
>
> 20 PASS out of 20 runs with overcommit_memory 2 on x86_64.
That is to be expected, since with overcommit_memory=2 we fail the
mmap() when the kernel does not think there is enough free memory. See
the part where we do:
if (map_blocks[i] == MAP_FAILED) {
map_count = i;
break;
}
It would be interesting to print the map_count and the value of i in
this fucntion and see where it breaks with overcommit_memory=2.
i.e.
if (map_blocks[i] == MAP_FAILED) {
tst_res(TINFO, "mmap() failed at %zu expected %zu",
i, map_count);
map_count = i;
break;
}
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-01-20 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 16:32 [LTP] [PATCH] tst_pollute_memory(): Set minimal safety margin to 64MB Martin Doucha
2021-01-19 12:43 ` Cyril Hrubis
2021-01-20 14:47 ` Naresh Kamboju
2021-01-20 14:54 ` Cyril Hrubis
2021-01-20 14:58 ` Naresh Kamboju
2021-01-20 15:06 ` Cyril Hrubis [this message]
2021-01-20 17:04 ` Naresh Kamboju
2021-01-20 17:07 ` Martin Doucha
2021-01-21 9:45 ` 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=YAhHAWTedDb/6Hd/@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