From: "Michal Koutný" <mkoutny@suse.com>
To: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Frederic Weisbecker <fweisbecker@suse.com>
Subject: [RFC PATCH 0/9] Add kernel cmdline option for rt_group_sched
Date: Mon, 16 Dec 2024 21:12:56 +0100 [thread overview]
Message-ID: <20241216201305.19761-1-mkoutny@suse.com> (raw)
Despite RT_GROUP_SCHED is only available on cgroup v1, there are still
some users of this feature. General purpose distros (e.g. [1][2][3][4])
cannot enable CONFIG_RT_GROUP_SCHED easily:
- since it prevents creation of RT tasks unless RT runtime is determined
and distributed into cgroup tree,
- grouping of RT threads is not what is desired by default on such
systems,
- it prevents use of cgroup v2 with RT tasks.
This changeset aims at deferring the decision whether to have
CONFIG_RT_GROUP_SCHED or not up until the boot time.
By default RT groups are available as originally but the user can
pass rt_group_sched=0 kernel cmdline parameter that disables the
grouping and behavior is like with !CONFIG_RT_GROUP_SCHED (with certain
runtime overhead).
The series is organized as follows:
1) generic ifdefs cleanup, no functional changes,
2) preparing root_task_group to be used in places that take shortcuts in
the case of !CONFIG_RT_GROUP_SCHED,
3) boot cmdline option that controls cgroup (v1) attributes,
4) conditional bypass of non-root task groups,
5) checks and comments refresh.
The crux are patches:
sched: Skip non-root task_groups with disabled RT_GROUP
sched: Bypass bandwitdh checks with runtime disabled RT_GROUP_SCHED
Futher notes:
- it is not sched_feat() flag because that can be flipped any time
- runtime disablement is not implemented as infinite per-cgroup RT limit
since that'd still employ group scheduling which is unlike
!CONFIG_RT_GROUP_SCHED
RFC notes:
- there remain two variants of various functions for
CONFIG_RT_GROUP_SCHED and !CONFIG_RT_GROUP_SCHED, those could be
folded into one and runtime evaluated guards in the folded functions
could be used (I haven't posted it yet due to unclear performance
benefit)
- I noticed some lockdep issues over rt_runtime_lock but those are also
in an unpatched kernel (and they seem to have been present since a
long time without complications)
[1] Debian (https://salsa.debian.org/kernel-team/linux/-/blob/debian/latest/debian/config/kernelarch-x86/config),
[2] ArchLinux (https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/blob/main/config),
[3] Fedora (https://src.fedoraproject.org/rpms/kernel/blob/rawhide/f/kernel-x86_64-fedora.config)
[4] openSUSE TW (https://github.com/SUSE/kernel-source/blob/stable/config/x86_64/default)
Michal Koutný (9):
sched: Convert CONFIG_RT_GROUP_SCHED macros to code conditions
sched: Remove unneeed macro wrap
sched: Always initialize rt_rq's task_group
sched: Add commadline option for RT_GROUP_SCHED toggling
sched: Skip non-root task_groups with disabled RT_GROUP_SCHED
sched: Bypass bandwitdh checks with runtime disabled RT_GROUP_SCHED
sched: Do not construct nor expose RT_GROUP_SCHED structures if
disabled
sched: Add RT_GROUP WARN checks for non-root task_groups
sched: Add annotations to RT_GROUP_SCHED fields
.../admin-guide/kernel-parameters.txt | 5 ++
init/Kconfig | 11 +++
kernel/sched/core.c | 69 +++++++++++++++----
kernel/sched/rt.c | 51 +++++++++-----
kernel/sched/sched.h | 34 +++++++--
kernel/sched/syscalls.c | 5 +-
6 files changed, 137 insertions(+), 38 deletions(-)
base-commit: f92f4749861b06fed908d336b4dee1326003291b
--
2.47.1
next reply other threads:[~2024-12-16 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 20:12 Michal Koutný [this message]
2024-12-16 20:12 ` [RFC PATCH 1/9] sched: Convert CONFIG_RT_GROUP_SCHED macros to code conditions Michal Koutný
2024-12-16 20:12 ` [RFC PATCH 2/9] sched: Remove unneeed macro wrap Michal Koutný
2024-12-16 20:12 ` [RFC PATCH 3/9] sched: Always initialize rt_rq's task_group Michal Koutný
2024-12-16 20:13 ` [RFC PATCH 4/9] sched: Add commadline option for RT_GROUP_SCHED toggling Michal Koutný
2024-12-16 20:13 ` [RFC PATCH 5/9] sched: Skip non-root task_groups with disabled RT_GROUP_SCHED Michal Koutný
2024-12-16 20:13 ` [RFC PATCH 6/9] sched: Bypass bandwitdh checks with runtime " Michal Koutný
2024-12-16 20:13 ` [RFC PATCH 7/9] sched: Do not construct nor expose RT_GROUP_SCHED structures if disabled Michal Koutný
2024-12-16 20:13 ` [RFC PATCH 8/9] sched: Add RT_GROUP WARN checks for non-root task_groups Michal Koutný
2024-12-16 20:13 ` [RFC PATCH 9/9] sched: Add annotations to RT_GROUP_SCHED fields Michal Koutný
2025-01-07 19:28 ` [RFC PATCH 0/9] Add kernel cmdline option for rt_group_sched Michal Koutný
2025-01-07 19:41 ` Peter Zijlstra
2025-01-10 10:04 ` Michal Koutný
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=20241216201305.19761-1-mkoutny@suse.com \
--to=mkoutny@suse.com \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=fweisbecker@suse.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®