From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 00/13] Convert LTP kernel/mem/testcase to New API
Date: Fri, 31 Mar 2017 03:09:54 -0400 (EDT) [thread overview]
Message-ID: <1856913062.17824117.1490944194254.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170330154358.GC886@rei.lan>
----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: "Li Wang" <liwang@redhat.com>
> Cc: ltp@lists.linux.it
> Sent: Thursday, 30 March, 2017 5:43:58 PM
> Subject: Re: [LTP] [RFC PATCH 00/13] Convert LTP kernel/mem/testcase to New API
>
> Hi!
> > Seems the failed reason in oom02/5 is not testcase issue, it just because
> > New API sets
> > test time in 5mins.
>
> The test_test structure has .timeout variable that, if set, overrides
> the default timeout. All you need to do is to to measure how long the
> test takes, then multiply it by something as 2 to be on a safe side
> and set the .timeout correspondingly.
OOM tests depend on amount of RAM+swap, so it's going to vary a lot.
I'd say safe side is in order of hours.
Other options that come to mind:
- formula based on amount of RAM and swap
- we measure how long it takes to fill 1GB of RAM/swap, and scale that up
- we run all OOM tests in mem cgroup with fixed mem/swap limit,
and set timeout according to worse case / slowest system
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
>
next prev parent reply other threads:[~2017-03-31 7:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 3:22 [LTP] [RFC PATCH 00/13] Convert LTP kernel/mem/testcase to New API Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 01/13] mem/lib: convert to new API Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 02/13] mem/oom: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 03/13] mem/ksm: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 04/13] mem/thp: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 05/13] mem/hugetlb: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 06/13] mem/hugemmap: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 07/13] mem/hugeshmat: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 08/13] mem/hugeshmctl: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 09/13] mm/hugeshmdt: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 10/13] mem/hugeshmget: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 11/13] mem/cpuset: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 12/13] mem/swapping: " Li Wang
2017-03-28 3:22 ` [LTP] [RFC PATCH 13/13] mem/tunable: " Li Wang
2017-03-30 15:55 ` [LTP] [RFC PATCH 01/13] mem/lib: " Cyril Hrubis
2017-03-31 6:36 ` Li Wang
2017-03-31 6:46 ` Cyril Hrubis
2017-03-30 15:43 ` [LTP] [RFC PATCH 00/13] Convert LTP kernel/mem/testcase to New API Cyril Hrubis
2017-03-31 6:01 ` Li Wang
2017-03-31 7:09 ` Jan Stancek [this message]
2017-03-31 7:34 ` 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=1856913062.17824117.1490944194254.JavaMail.zimbra@redhat.com \
--to=jstancek@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