The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>
Cc: David Vernet <void@manifault.com>,
	Changwoo Min <changwoo@igalia.com>,
	sched-ext@lists.linux.dev, Emil Tsalapatis <emil@etsalapatis.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET sched_ext/for-7.3] sched_ext: Rename the cid-form cgroup ops to cpuctl_*
Date: Mon, 20 Jul 2026 08:29:49 +0200	[thread overview]
Message-ID: <al3AXT4K6CuURSxE@gpd4> (raw)
In-Reply-To: <20260718101029.725350-1-tj@kernel.org>

On Sat, Jul 18, 2026 at 12:10:27AM -1000, Tejun Heo wrote:
> Hello,
> 
> Two unrelated things go by "cgroup" in the cid form. Sub-schedulers attach
> to cgroups, and the cgroup_*() ops deliver cpu controller events. While the
> ops names suggest cgroup2 hierarchy, they actually operate on the cpu
> controller. The cid form has no users beyond scx_qmap yet, so rename the
> ops to cpuctl_* while the ABI can still change. The cpu form is deployed
> ABI and keeps the old names.

Conceptually it makes sense, cpuctl_* is a more precise terminology since these
callbacks report CPU-controller events.

This breaks existing CID-form schedulers, but I guess it's fine, since we don't
have any user of the CID-form API right now (except scx_qmap, which is in tree),
so we should be fine with that.

Reviewed-by: Andrea Righi <arighi@nvidia.com>

-Andrea

> 
> - 0001 factors the skeleton open path out of SCX_OPS_OPEN() and adds
>   SCX_OPS_CID_OPEN() so that cid-form skeletons don't depend on the
>   cpu-form member names dereferenced by the compat clears.
> 
> - 0002 renames the ops to cpuctl_* in struct sched_ext_ops_cid and updates
>   scx_qmap, the only cid-form scheduler.
> 
> Based on sched_ext/for-7.3 (7c2cd767705d) plus the cgroup migration
> patchset:
> 
>   https://lore.kernel.org/r/20260718081727.582037-1-tj@kernel.org
> 
> Tejun Heo (2):
>   tools/sched_ext: Add SCX_OPS_CID_OPEN for cid-form schedulers
>   sched_ext: Rename the cid-form cgroup ops to cpuctl_*
> 
> Git tree: git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-cpuctl-rename
> 
>  kernel/sched/ext/ext.c               | 36 ++++++++++++++++++------------------
>  kernel/sched/ext/internal.h          | 25 ++++++++++++-------------
>  tools/sched_ext/include/scx/compat.h | 30 ++++++++++++++++++++++--------
>  tools/sched_ext/scx_qmap.bpf.c       | 22 +++++++++++-----------
>  tools/sched_ext/scx_qmap.c           |  4 ++--
>  tools/sched_ext/scx_qmap.h           |  2 +-
>  6 files changed, 66 insertions(+), 53 deletions(-)
> 
> --
> tejun

  parent reply	other threads:[~2026-07-20  6:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18 10:10 [PATCHSET sched_ext/for-7.3] sched_ext: Rename the cid-form cgroup ops to cpuctl_* Tejun Heo
2026-07-18 10:10 ` [PATCH 1/2] tools/sched_ext: Add SCX_OPS_CID_OPEN for cid-form schedulers Tejun Heo
2026-07-18 10:10 ` [PATCH 2/2] sched_ext: Rename the cid-form cgroup ops to cpuctl_* Tejun Heo
2026-07-20  6:29 ` Andrea Righi [this message]
2026-07-20  7:37 ` [PATCHSET sched_ext/for-7.3] " 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=al3AXT4K6CuURSxE@gpd4 \
    --to=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=emil@etsalapatis.com \
    --cc=linux-kernel@vger.kernel.org \
    --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