From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v1 2/4] mem: take use of new cgroup API
Date: Wed, 27 May 2020 03:45:18 -0400 (EDT) [thread overview]
Message-ID: <396532423.13763181.1590565518615.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200527031430.22144-2-liwang@redhat.com>
> diff --git a/testcases/kernel/mem/cpuset/cpuset01.c
> b/testcases/kernel/mem/cpuset/cpuset01.c
> index 853f7fe55..cecc4ba86 100644
> --- a/testcases/kernel/mem/cpuset/cpuset01.c
> +++ b/testcases/kernel/mem/cpuset/cpuset01.c
> @@ -51,11 +51,11 @@ static void test_cpuset(void)
> unsigned long nmask[MAXNODES / BITS_PER_LONG] = { 0 };
> char mems[BUFSIZ], buf[BUFSIZ];
>
> - read_cpuset_files(CPATH, "cpus", buf);
> - write_cpuset_files(CPATH_NEW, "cpus", buf);
> - read_cpuset_files(CPATH, "mems", mems);
> - write_cpuset_files(CPATH_NEW, "mems", mems);
> - SAFE_FILE_PRINTF(CPATH_NEW "/tasks", "%d", getpid());
> + read_cpuset_files(PATH_TMP_CG1_CST, "cpus", buf);
> + write_cpuset_files(PATH_CG1_CST_LTP, "cpus", buf);
> + read_cpuset_files(PATH_TMP_CG1_CST, "mems", mems);
> + write_cpuset_files(PATH_CG1_CST_LTP, "mems", mems);
This mixes generic api with cgroup1. It currently relies on implementation
detail of tst_cgroup_mount(), which isn't visible just by looking at this test.
We should make it generic or make it clear that test is for cgroup1 only:
setup()
if (tst_cgroup_version() != TST_CGROUP_V1)
TCONF
> diff --git a/testcases/kernel/mem/oom/oom03.c
> b/testcases/kernel/mem/oom/oom03.c
> index ce0b34c31..af3a565ce 100644
> --- a/testcases/kernel/mem/oom/oom03.c
> +++ b/testcases/kernel/mem/oom/oom03.c
> @@ -36,27 +36,26 @@
>
> #ifdef HAVE_NUMA_V2
>
> -static int memcg_mounted;
> -
> static void verify_oom(void)
> {
> #ifdef TST_ABI32
> tst_brk(TCONF, "test is not designed for 32-bit system.");
> #endif
>
> - SAFE_FILE_PRINTF(MEMCG_PATH_NEW "/tasks", "%d", getpid());
> - SAFE_FILE_PRINTF(MEMCG_LIMIT, "%ld", TESTMEM);
> + tst_cgroup_mem_set_maxbytes(TESTMEM);
>
> testoom(0, 0, ENOMEM, 1);
>
> - if (access(MEMCG_SW_LIMIT, F_OK) == -1) {
> + if ((access(PATH_MEMORY_SW_LIMIT, F_OK) == -1) ||
> + (access(PATH_MEMORY_SW_MAX, F_OK) == -1)) {
This could be tst_cgroup_mem_swapacct_enabled(), without need for test
to probe specific cgroup[12] files.
next prev parent reply other threads:[~2020-05-27 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 3:14 [LTP] [PATCH v1 1/4] lib: add new cgroup test API Li Wang
2020-05-27 3:14 ` [LTP] [PATCH v1 2/4] mem: take use of new cgroup API Li Wang
2020-05-27 7:45 ` Jan Stancek [this message]
2020-05-27 10:10 ` Li Wang
2020-05-27 3:14 ` [LTP] [PATCH v1 3/4] mem: remove the old " Li Wang
2020-05-27 3:14 ` [LTP] [PATCH v1 4/4] mm: add cpuset01 to runtest file Li Wang
2020-05-27 7:40 ` [LTP] [PATCH v1 1/4] lib: add new cgroup test API Jan Stancek
2020-05-27 8:00 ` Li Wang
2020-05-27 9:15 ` Jan Stancek
2020-05-27 7:47 ` Jan Stancek
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=396532423.13763181.1590565518615.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