All of lore.kernel.org
 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
Subject: [PATCHSET sched_ext/for-7.3] sched_ext: Bandwidth-limited rescue execution for stranded tasks
Date: Fri, 31 Jul 2026 22:51:38 -1000	[thread overview]
Message-ID: <20260801085150.2697653-1-tj@kernel.org> (raw)

Hello,

A sub-scheduler holds only the cids its parent granted and nothing
guarantees that they cover its tasks' affinities. A task that can run on
none of them currently has no good ending: the scheduler's insert is
cap-rejected and reenqueued until the repeat limit ejects the scheduler, or
the task stalls into the watchdog.

This series adds kernel-side rescue execution. A scheduler marks an insert
that may be cap-rejected with SCX_ENQ_RESCUE and the kernel, instead of
bouncing it, runs the task on the target cpu at a small configured
bandwidth. A rescue starts out non-disruptive. Schedulers that hold caps on
the cid largely stay in control of the cpu - a preemption cap, for example,
still lets its holder preempt the rescuee. When a rescue goes unserved for
too long, it escalates into protected execution.

When a cpu's rescue queue stays oversaturated past the overload threshold,
the kernel ejects the sub-scheduler with the highest recent rescue
consumption on that cpu instead of misblaming the waiter's owner.

- 0001-0005 are preps: naming, helper visibility, dsq-move flag vetting and
  the IGNORE_CAPS preemption waiver.
- 0006-0007 synchronize slice/dsq_vtime writes at insertion commit and add
  SCX_TASK_PROTECTED, the groundwork that lets a kernel-granted slice
  survive scheduler writes.
- 0008-0009 add the rescue machinery and the overload ejection.
- 0010 syncs the tools autogen enum headers.
- 0011-0012 fix scx_qmap's pinned-task direct dispatch and add rescue
  support as the demonstration consumer.

 0001-sched_ext-Rename-scx_local_or_reject_dsq-to-scx_reso.patch
 0002-sched_ext-Make-several-ext.c-helpers-available-outsi.patch
 0003-sched_ext-Factor-out-__scx_bpf_now.patch
 0004-sched_ext-Reject-internal-enq_flags-in-the-dsq-move-.patch
 0005-sched_ext-Make-SCX_ENQ_IGNORE_CAPS-waive-the-preempt.patch
 0006-sched_ext-Synchronize-slice-and-dsq_vtime-writes.patch
 0007-sched_ext-Add-SCX_TASK_PROTECTED.patch
 0008-sched_ext-Add-bandwidth-limited-rescue-execution-for.patch
 0009-sched_ext-Eject-the-top-rescue-consumer-on-overload.patch
 0010-sched_ext-Sync-tools-autogen-enum-headers.patch
 0011-sched_ext-scx_qmap-Idle-check-pinned-tasks-before-di.patch
 0012-sched_ext-scx_qmap-Add-rescue-support.patch

Based on sched_ext/for-7.3 (ee7aece60817).

Git tree: git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-rescue-v1

 include/linux/sched/ext.h                       |   7 +
 kernel/sched/ext/ext.c                          | 690 ++++++++++++++++--------
 kernel/sched/ext/internal.h                     |  78 ++-
 kernel/sched/ext/sub.c                          | 496 ++++++++++++++++-
 kernel/sched/ext/sub.h                          |  41 +-
 kernel/sched/ext/types.h                        |  12 +
 kernel/sched/sched.h                            |  13 +
 tools/sched_ext/include/scx/enum_defs.autogen.h |  16 +
 tools/sched_ext/include/scx/enums.autogen.bpf.h |   3 +
 tools/sched_ext/include/scx/enums.autogen.h     |   1 +
 tools/sched_ext/scx_qmap.bpf.c                  |  88 +--
 tools/sched_ext/scx_qmap.c                      |  23 +-
 tools/sched_ext/scx_qmap.h                      |   1 +
 13 files changed, 1186 insertions(+), 283 deletions(-)

--
tejun

             reply	other threads:[~2026-08-01  8:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01  8:51 Tejun Heo [this message]
2026-08-01  8:51 ` [PATCH 01/12] sched_ext: Rename scx_local_or_reject_dsq() to scx_resolve_local_dsq() Tejun Heo
2026-08-01  8:51 ` [PATCH 02/12] sched_ext: Make several ext.c helpers available outside ext.c Tejun Heo
2026-08-01  8:58   ` sashiko-bot
2026-08-01  8:51 ` [PATCH 03/12] sched_ext: Factor out __scx_bpf_now() Tejun Heo
2026-08-01  8:51 ` [PATCH 04/12] sched_ext: Reject internal enq_flags in the dsq move kfuncs Tejun Heo
2026-08-01  8:51 ` [PATCH 05/12] sched_ext: Make SCX_ENQ_IGNORE_CAPS waive the preemption cap too Tejun Heo
2026-08-01  8:51 ` [PATCH 06/12] sched_ext: Synchronize slice and dsq_vtime writes Tejun Heo
2026-08-01  8:51 ` [PATCH 07/12] sched_ext: Add SCX_TASK_PROTECTED Tejun Heo
2026-08-01  8:51 ` [PATCH 08/12] sched_ext: Add bandwidth-limited rescue execution for stranded tasks Tejun Heo
2026-08-01  8:51 ` [PATCH 09/12] sched_ext: Eject the top rescue consumer on overload Tejun Heo
2026-08-01  9:11   ` sashiko-bot
2026-08-01  8:51 ` [PATCH 10/12] sched_ext: Sync tools autogen enum headers Tejun Heo
2026-08-01  8:51 ` [PATCH 11/12] sched_ext: scx_qmap - Idle-check pinned tasks before direct dispatch Tejun Heo
2026-08-01  9:06   ` sashiko-bot
2026-08-01  8:51 ` [PATCH 12/12] sched_ext: scx_qmap - Add rescue support Tejun Heo
2026-08-01  9:06   ` sashiko-bot

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=20260801085150.2697653-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 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.