From: Zhe Liu <liuzhe1@kylinos.cn>
To: tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com,
corbet@lwn.net, mingo@redhat.com, peterz@infradead.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org
Cc: skhan@linuxfoundation.org, rdunlap@infradead.org,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
kprateek.nayak@amd.com, dtcccc@linux.alibaba.com,
changhuaixin@linux.alibaba.com, shanpeic@linux.alibaba.com,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Zhe Liu <liuzhe1@kylinos.cn>
Subject: [PATCH v3 0/3] sched/fair: remove quota/burst write-order dependency
Date: Fri, 11 Sep 2026 17:22:55 +0800 [thread overview]
Message-ID: <20260911092258.660771-1-liuzhe1@kylinos.cn> (raw)
The CPU bandwidth quota and burst controls currently make the order of
userspace writes significant. A burst configured while quota is unlimited
can prevent a later finite quota from being installed, and updating the
burst before increasing the quota can fail with -EINVAL.
Remove the write-order dependency by decoupling burst validation from the
current quota. The previous quota-relative checks implicitly limited the
maximum configurable burst to max_bw_runtime_us / 2 for a finite quota,
so retain that limit as an independent upper bound.
Keep the configured burst unchanged across quota updates, and cap the
burst actually available at refill time to min(burst, quota). This allows
cpu.max and cpu.max.burst to be updated in either order without changing
the maximum burst previously allowed for a finite quota.
The series also adds a selftest covering both write orders and documents
the resulting behavior for cgroup v1 and cgroup v2.
---
Changes in v3:
- Use max_bw_runtime_us / 2 as an independent upper bound for burst,
preserving the maximum burst previously allowed with a finite quota
while removing its dependency on the current quota.
- Drop Cc: stable@vger.kernel.org from patch 1.
- Update the cpu.max.burst documentation to describe the configured burst
independently of the current quota and the quota-relative clamp applied
at runtime refill.
Changes in v2:
- Keep the configured burst independent of quota changes instead of
adjusting or resetting it when the quota is updated.
- Move the quota-relative restriction to the CFS runtime refill path,
where the effective burst is capped to the current quota.
- Add selftests covering quota and burst updates in both write orders and
document the resulting behavior for cgroup v1 and cgroup v2.
v2: https://lore.kernel.org/all/20260904062013.504236-1-liuzhe1@kylinos.cn/
v1: https://lore.kernel.org/all/20260820033218.214259-1-liuzhe1@kylinos.cn/
Zhe Liu (3):
sched/fair: remove quota/burst write-order dependency
selftests: cgroup: test CPU quota and burst write order
docs: cgroup-v2: document CPU quota and burst ordering
Documentation/admin-guide/cgroup-v2.rst | 7 +++-
Documentation/scheduler/sched-bwc.rst | 22 ++++++++-----
kernel/sched/core.c | 3 +-
kernel/sched/fair.c | 3 +-
tools/testing/selftests/cgroup/test_cpu.c | 40 +++++++++++++++++++++++
5 files changed, 62 insertions(+), 13 deletions(-)
base-commit: df2908090cda368b01ff43709f51890076c56157
--
2.25.1
next reply other threads:[~2026-09-11 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 9:22 Zhe Liu [this message]
2026-09-11 9:22 ` [PATCH v3 1/3] sched/fair: remove quota/burst write-order dependency Zhe Liu
2026-09-11 9:22 ` [PATCH v3 2/3] selftests: cgroup: test CPU quota and burst write order Zhe Liu
2026-09-11 9:22 ` [PATCH v3 3/3] docs: cgroup-v2: document CPU quota and burst ordering 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=20260911092258.660771-1-liuzhe1@kylinos.cn \
--to=liuzhe1@kylinos.cn \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=changhuaixin@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=dtcccc@linux.alibaba.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=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shanpeic@linux.alibaba.com \
--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;
as well as URLs for NNTP newsgroup(s).