From: Zhouping Liu <zliu@redhat.com>
To: LTP List <ltp-list@lists.sourceforge.net>
Subject: [LTP] [PATCH v2 0/7] mm/oom: extend the coverage of OOM
Date: Fri, 15 Mar 2013 23:03:05 +0800 [thread overview]
Message-ID: <cover.1363358877.git.zliu@redhat.com> (raw)
changed log from v1 to v2:
1. added a new is_numa() function instead of ISNUMA global variable;
2. added new patch to remove the prefix underscroe '_' of the
internal function name;
3. used SAFE_FILE_SCANF() instead of read_file().
4. some cleanup...
The patch set updated all OOM testcases, and added a new testcase.
Inside old version, OOM only test MPOL_MBIND mempolicy in NUMA
system, and the combination of CPUSET, MEMCG & NUMA is complex,
and not clear. Also CPUSET is only used in NUMA system.
These patch set adjust them, now we can coverage the below tests:
1) OOM under normal - oom01
2) OOM under all mempolicy - oom02
3) OOM under MEMCG (+ mempolicy) - oom03
4) OOM under CPUSET (+ mempolicy) - oom04
5) OOM under CPUSET & MEMCG - oom05
tested the V2 patch set, no regression found.
Zhouping Liu (7):
lib/mem: modified _gather_cpus() as _gather_node_cpus()
mm/oom02: modified 'OOM for NUMA' as 'OOM for mempolicy'
numa_helper: added a new function is_numa()
mm/oom0[3|4]: added 'OOM for CPUSET' and moved 'OOM with MEMCG &
numa' to oom03
lib/mem: updated testoom() and oom() funcs
mm/oom05: new testcase
lib/mem: removed the prefix underscore '_' of the internal function
name
runtest/mm | 1 +
testcases/kernel/include/numa_helper.h | 1 +
testcases/kernel/lib/numa_helper.c | 25 ++++++
testcases/kernel/mem/include/mem.h | 4 +-
testcases/kernel/mem/lib/mem.c | 145 ++++++++++++++++++++------------
testcases/kernel/mem/oom/oom01.c | 6 +-
testcases/kernel/mem/oom/oom02.c | 20 +++--
testcases/kernel/mem/oom/oom03.c | 24 +++++-
testcases/kernel/mem/oom/oom04.c | 60 ++++++--------
testcases/kernel/mem/oom/oom05.c | 147 +++++++++++++++++++++++++++++++++
10 files changed, 328 insertions(+), 105 deletions(-)
create mode 100644 testcases/kernel/mem/oom/oom05.c
--
1.7.11.7
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2013-03-15 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 15:03 Zhouping Liu [this message]
2013-03-15 15:03 ` [LTP] [PATCH v2 1/7] lib/mem: modified _gather_cpus() as _gather_node_cpus() Zhouping Liu
2013-03-15 15:03 ` [LTP] [PATCH v2 2/7] mm/oom02: modified 'OOM for NUMA' as 'OOM for mempolicy' Zhouping Liu
2013-03-15 15:03 ` [LTP] [PATCH v2 3/7] numa_helper: added a new function is_numa() Zhouping Liu
2013-03-15 16:09 ` Jan Stancek
2013-03-18 2:33 ` Zhouping Liu
2013-03-15 15:03 ` [LTP] [PATCH v2 4/7] mm/oom0[3|4]: added 'OOM for CPUSET' and moved 'OOM with MEMCG & numa' to oom03 Zhouping Liu
2013-03-15 15:03 ` [LTP] [PATCH v2 5/7] lib/mem: updated testoom() and oom() funcs Zhouping Liu
2013-03-15 15:03 ` [LTP] [PATCH v2 6/7] mm/oom05: new testcase Zhouping Liu
2013-03-15 15:03 ` [LTP] [PATCH v2 7/7] lib/mem: removed the prefix underscore '_' of the internal function name Zhouping Liu
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=cover.1363358877.git.zliu@redhat.com \
--to=zliu@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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