From: Zhe Liu <liuzhe1@kylinos.cn>
To: mkoutny@suse.com
Cc: bsegall@google.com, cgroups@vger.kernel.org, corbet@lwn.net,
dietmar.eggemann@arm.com, hannes@cmpxchg.org,
juri.lelli@redhat.com, kprateek.nayak@amd.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, liuzhe1@kylinos.cn,
mgorman@suse.de, mingo@redhat.com, peterz@infradead.org,
rostedt@goodmis.org, skhan@linuxfoundation.org, tj@kernel.org,
vincent.guittot@linaro.org, vschneid@redhat.com
Subject: [PATCH v2 2/3] selftests: cgroup: Test CPU quota and burst write order
Date: Fri, 4 Sep 2026 14:20:12 +0800 [thread overview]
Message-ID: <20260904062013.504236-3-liuzhe1@kylinos.cn> (raw)
In-Reply-To: <20260904062013.504236-1-liuzhe1@kylinos.cn>
Test that quota and burst can be written in either order without losing
the configured burst value.
Signed-off-by: Zhe Liu <liuzhe1@kylinos.cn>
---
tools/testing/selftests/cgroup/test_cpu.c | 40 +++++++++++++++++++++++
1 file changed, 40 insertions(+)
diff --git a/tools/testing/selftests/cgroup/test_cpu.c b/tools/testing/selftests/cgroup/test_cpu.c
index f9f7017d9299..b13c2535afcd 100644
--- a/tools/testing/selftests/cgroup/test_cpu.c
+++ b/tools/testing/selftests/cgroup/test_cpu.c
@@ -733,6 +733,45 @@ static int test_cpucg_max(const char *root)
return ret;
}
+static int test_cpucg_max_burst(const char *root)
+{
+ int ret = KSFT_FAIL;
+ char *cpucg;
+
+ cpucg = cg_name(root, "cpucg_max_burst");
+ if (!cpucg)
+ return KSFT_FAIL;
+
+ if (cg_create(cpucg))
+ goto cleanup;
+
+ if (cg_write(cpucg, "cpu.max", "max 100000") ||
+ cg_write(cpucg, "cpu.max.burst", "100000000") ||
+ cg_write(cpucg, "cpu.max", "50000 100000") ||
+ cg_read_strcmp(cpucg, "cpu.max.burst", "100000000\n"))
+ goto cleanup;
+
+ if (cg_write(cpucg, "cpu.max.burst", "80000") ||
+ cg_write(cpucg, "cpu.max", "100000 100000") ||
+ cg_read_strcmp(cpucg, "cpu.max.burst", "80000\n"))
+ goto cleanup;
+
+ if (cg_write(cpucg, "cpu.max.burst", "0") ||
+ cg_write(cpucg, "cpu.max", "50000 100000") ||
+ cg_write(cpucg, "cpu.max", "100000 100000") ||
+ cg_write(cpucg, "cpu.max.burst", "80000") ||
+ cg_read_strcmp(cpucg, "cpu.max.burst", "80000\n"))
+ goto cleanup;
+
+ ret = KSFT_PASS;
+
+cleanup:
+ cg_destroy(cpucg);
+ free(cpucg);
+
+ return ret;
+}
+
/*
* This test verifies that a process inside of a nested cgroup whose parent
* group has a cpu.max value set, is properly throttled.
@@ -822,6 +861,7 @@ struct cpucg_test {
T(test_cpucg_nested_weight_overprovisioned),
T(test_cpucg_nested_weight_underprovisioned),
T(test_cpucg_max),
+ T(test_cpucg_max_burst),
T(test_cpucg_max_nested),
};
#undef T
--
2.25.1
next prev parent reply other threads:[~2026-09-04 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 3:32 [PATCH 0/2] sched/fair: Reset incompatible burst on quota change Zhe Liu
2026-08-20 3:32 ` [PATCH 1/2] " Zhe Liu
2026-08-20 11:43 ` Michal Koutný
2026-08-26 3:00 ` Zhe Liu
2026-09-04 6:20 ` [PATCH v2 0/3] sched/fair: remove quota/burst write-order dependency Zhe Liu
2026-09-04 6:20 ` [PATCH v2 1/3] sched/fair: Remove the write-order dependency between cpu.max and cpu.max.burst Zhe Liu
2026-09-04 9:21 ` Tao Cui
2026-09-04 6:20 ` Zhe Liu [this message]
2026-09-04 6:20 ` [PATCH v2 3/3] Documentation: describe CPU quota and burst ordering Zhe Liu
2026-08-20 3:32 ` [PATCH 2/2] Documentation: describe burst reset on quota changes Zhe 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=20260904062013.504236-3-liuzhe1@kylinos.cn \
--to=liuzhe1@kylinos.cn \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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