The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>,
	Andrea Righi <arighi@nvidia.com>,
	Changwoo Min <changwoo@igalia.com>
Cc: sched-ext@lists.linux.dev, Emil Tsalapatis <emil@etsalapatis.com>,
	linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: [PATCHSET v2 sched_ext/for-7.3] sched_ext: Sub-scheduler and cid fixes
Date: Tue, 21 Jul 2026 12:31:14 -1000	[thread overview]
Message-ID: <20260721223118.2268529-1-tj@kernel.org> (raw)

Hello,

v2: v1's 0003 only added NULL checks and, as Andrea and sashiko-bot pointed
    out, left the cid tables readable while being filled and rewritten in
    place. The new 0004 replaces it: each root enable builds a fresh table
    set privately and publishes it with RCU once the layout is final. 0003
    is a new trivial dead code removal. 0001-0002 are unchanged.

v1: https://lore.kernel.org/r/20260720082605.1451945-1-tj@kernel.org

A few fixes for the sub-scheduler and cid-form code on for-7.3.

- 0001 attributes a runnable stall to the scheduler that owns the DSQ the
  task is stuck on rather than the task's owner, so a bypassing sub's task
  parked on an ancestor's bypass DSQ blames the ancestor, not the sub.

- 0002 skips the default CPU selection while bypassing. The pick is discarded
  by the bypass enqueue anyway, and it consults idle masks a scheduler doing
  its own idle tracking leaves frozen.

- 0003 drops the unused scx_cpumask_to_cmask().

- 0004 ties the cid tables' lifetimes to the root sched: built privately on
  enable, published with RCU once final, unpublished and RCU-freed on
  disable.

Based on sched_ext/for-7.3 (b20dfde5ec54).

Tejun Heo (4):
  sched_ext: Blame the DSQ's owning scheduler for a runnable stall
  sched_ext: Skip the default CPU selection while bypassing
  sched_ext: Drop unused scx_cpumask_to_cmask()
  sched_ext: Build the cid tables privately and publish them with RCU

Git tree: git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-sub-fixes-v2

 kernel/sched/ext/cid.c      | 279 ++++++++++++++++++++++++++------------------
 kernel/sched/ext/cid.h      |  58 +++++----
 kernel/sched/ext/ext.c      |  80 ++++++++++---
 kernel/sched/ext/internal.h |   5 +-
 kernel/sched/ext/sub.c      |  42 +++++--
 5 files changed, 298 insertions(+), 166 deletions(-)

--
tejun

             reply	other threads:[~2026-07-21 22:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 22:31 Tejun Heo [this message]
2026-07-21 22:31 ` [PATCH v2 1/4] sched_ext: Blame the DSQ's owning scheduler for a runnable stall Tejun Heo
2026-07-21 22:31 ` [PATCH v2 2/4] sched_ext: Skip the default CPU selection while bypassing Tejun Heo
2026-07-21 22:31 ` [PATCH v2 3/4] sched_ext: Drop unused scx_cpumask_to_cmask() Tejun Heo
2026-07-21 22:31 ` [PATCH v2 4/4] sched_ext: Build the cid tables privately and publish them with RCU Tejun Heo
2026-07-22  7:30   ` Andrea Righi
2026-07-22  8:23   ` [PATCH v3 " Tejun Heo
2026-07-22  8:29     ` Andrea Righi
2026-07-22  8:00 ` [PATCHSET v2 sched_ext/for-7.3] sched_ext: Sub-scheduler and cid fixes Andrea Righi
2026-07-22  8:34 ` 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=20260721223118.2268529-1-tj@kernel.org \
    --to=tj@kernel.org \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=emil@etsalapatis.com \
    --cc=linux-kernel@vger.kernel.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