From: Tejun Heo <tj@kernel.org>
To: mingo@redhat.com, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, sched-ext@lists.linux.dev,
void@manifault.com, arighi@nvidia.com, changwoo@igalia.com
Subject: [PATCHSET tip/sched/core] sched/core: Reorganize bandwidth control interface handling
Date: Fri, 13 Jun 2025 15:23:26 -1000 [thread overview]
Message-ID: <20250614012346.2358261-1-tj@kernel.org> (raw)
Reorganize cgroup bandwidth control interface handling in preparation of
sched_ext support.
- Implement tg_bandwidth() and tg_set_bandwidth() to centralize parameter
reads and updates.
- Cleanly delineate time unit boundary - durations are in usecs from the
interface files upto tg[_set]_bandwidth(). The fair functions that are
called by tg[_set]_bandwidth() map them to nsecs.
This reorganization will allow sched_ext to plug into tg[_set]_bandwidth()
the same way it plugs into tg_weight(). No functional changes intended.
0001-sched-fair-Move-max_cfs_quota_period-decl-and-defaul.patch
0002-sched-core-Relocate-tg_get_cfs_-and-cpu_cfs_-_read_.patch
0003-sched-core-Reorganize-cgroup-bandwidth-control-inter.patch
0004-sched-core-Reorganize-cgroup-bandwidth-control-inter.patch
The patchset is on top of tip/sched/core (dabe1be4e84c ("sched/smp: Use the
SMP version of double_rq_clock_clear_update()")) and also available in the
following git branch:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git reorg-bandwidth-control
diffstat follows. Thanks.
kernel/sched/core.c | 311 ++++++++++++++++++++++++++++++++++++++++-------------------------------------
kernel/sched/fair.c | 15 ---
kernel/sched/sched.h | 13 +++
3 files changed, 178 insertions(+), 161 deletions(-)
--
tejun
next reply other threads:[~2025-06-14 1:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 1:23 Tejun Heo [this message]
2025-06-14 1:23 ` [PATCH 1/4] sched/fair: Move max_cfs_quota_period decl and default_cfs_period() def from fair.c to sched.h Tejun Heo
2025-06-20 9:49 ` [tip: sched/core] " tip-bot2 for Tejun Heo
2025-06-14 1:23 ` [PATCH 2/4] sched/core: Relocate tg_get_cfs_*() and cpu_cfs_*_read_*() Tejun Heo
2025-06-20 9:49 ` [tip: sched/core] " tip-bot2 for Tejun Heo
2025-06-14 1:23 ` [PATCH 3/4] sched/core: Reorganize cgroup bandwidth control interface file reads Tejun Heo
2025-06-20 9:49 ` [tip: sched/core] " tip-bot2 for Tejun Heo
2025-06-14 1:23 ` [PATCH 4/4] sched/core: Reorganize cgroup bandwidth control interface file writes Tejun Heo
2025-06-20 9:49 ` [tip: sched/core] " tip-bot2 for Tejun Heo
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=20250614012346.2358261-1-tj@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.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®