From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>
Cc: linux-kernel@vger.kernel.org, sched-ext@lists.linux.dev,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH sched_ext/for-6.17 2/2] sched_ext: Add support for cgroup bandwidth control interface
Date: Fri, 20 Jun 2025 17:04:26 -1000 [thread overview]
Message-ID: <aFYhOpvAOC-Fc6Rc@slm.duckdns.org> (raw)
In-Reply-To: <aEzRnjYmqxbOU-3z@slm.duckdns.org>
On Fri, Jun 13, 2025 at 03:34:22PM -1000, Tejun Heo wrote:
> From 077814f57f8acce13f91dc34bbd2b7e4911fbf25 Mon Sep 17 00:00:00 2001
> From: Tejun Heo <tj@kernel.org>
> Date: Fri, 13 Jun 2025 15:06:47 -1000
>
> - Add CONFIG_GROUP_SCHED_BANDWIDTH which is selected by both
> CONFIG_CFS_BANDWIDTH and EXT_GROUP_SCHED.
>
> - Put bandwidth control interface files for both cgroup v1 and v2 under
> CONFIG_GROUP_SCHED_BANDWIDTH.
>
> - Update tg_bandwidth() to fetch configuration parameters from fair if
> CONFIG_CFS_BANDWIDTH, SCX otherwise.
>
> - Update tg_set_bandwidth() to update the parameters for both fair and SCX.
>
> - Add bandwidth control parameters to struct scx_cgroup_init_args.
>
> - Add sched_ext_ops.cgroup_set_bandwidth() which is invoked on bandwidth
> control parameter updates.
>
> - Update scx_qmap and maximal selftest to test the new feature.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
Applied 1-2 to sched_ext/for-6.17.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-06-21 3:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 1:33 [PATCH sched_ext/for-6.17 1/2] sched_ext, sched/core: Factor out struct scx_task_group Tejun Heo
2025-06-14 1:34 ` [PATCH sched_ext/for-6.17 2/2] sched_ext: Add support for cgroup bandwidth control interface Tejun Heo
2025-06-21 3:04 ` Tejun Heo [this message]
2025-06-17 8:50 ` [PATCH sched_ext/for-6.17 1/2] sched_ext, sched/core: Factor out struct scx_task_group Peter Zijlstra
2025-06-17 18:21 ` Tejun Heo
2025-06-20 9:44 ` Peter Zijlstra
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=aFYhOpvAOC-Fc6Rc@slm.duckdns.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.