From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>
Cc: Waiman Long <longman@redhat.com>,
Michal Koutny <mkoutny@suse.com>,
sched-ext@lists.linux.dev, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCHSET v2 sched_ext/for-7.4] sched_ext: Add scx_bpf_cgroup_nr_cpus()
Date: Wed, 30 Sep 2026 11:00:17 +0200 [thread overview]
Message-ID: <20260930090049.1035813-1-arighi@nvidia.com> (raw)
Hierarchical BPF schedulers need to know how many CPUs a cgroup can run
on when distributing group-wide weights. For example, fair's group share
calculation scales a group's weight by the smaller of its estimated
runnable task count and the number of CPUs in its effective cpuset.
Without that count, a BPF scheduler can only use the machine-wide CPU
count and may give a group confined to a few CPUs excessive shares.
This series adds scx_bpf_cgroup_nr_cpus(), a kfunc that returns the same
count fair uses. This allows scx_eevdf to compute per-cgroup shares for
groups confined to a subset of CPUs through cpuset. A selftest covers
effective and inherited cpusets, changes to the allowed CPUs, and calls
with and without a scheduler attached.
This series requires Waiman Long's cpuset fix to avoid a potential
use-after-free in a rare cgroup filesystem rebind race:
https://lore.kernel.org/r/20260930031833.660267-1-longman@redhat.com
Changes in v2:
- Drop the cpuset RCU guard patch
- Link to v1:
https://lore.kernel.org/r/20260929084124.626693-1-arighi@nvidia.com
Andrea Righi (2):
sched_ext: Introduce scx_bpf_cgroup_nr_cpus()
selftests/sched_ext: Test scx_bpf_cgroup_nr_cpus()
kernel/sched/ext/ext.c | 18 +
tools/sched_ext/include/scx/common.bpf.h | 1 +
tools/sched_ext/include/scx/compat.bpf.h | 7 +
tools/testing/selftests/sched_ext/Makefile | 6 +-
.../selftests/sched_ext/cgroup_nr_cpus.bpf.c | 60 +++
.../selftests/sched_ext/cgroup_nr_cpus.c | 419 ++++++++++++++++++
tools/testing/selftests/sched_ext/config | 1 +
7 files changed, 510 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/sched_ext/cgroup_nr_cpus.bpf.c
create mode 100644 tools/testing/selftests/sched_ext/cgroup_nr_cpus.c
--
2.55.0
next reply other threads:[~2026-09-30 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 9:00 Andrea Righi [this message]
2026-09-30 9:00 ` [PATCH 1/2] sched_ext: Introduce scx_bpf_cgroup_nr_cpus() Andrea Righi
2026-09-30 9:00 ` [PATCH 2/2] selftests/sched_ext: Test scx_bpf_cgroup_nr_cpus() Andrea Righi
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=20260930090049.1035813-1-arighi@nvidia.com \
--to=arighi@nvidia.com \
--cc=cgroups@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--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®