Re: [PATCH 1/2] sched/doc: add a preemption model overview
From: Quchaosheng
Date: Tue Sep 22 2026 - 03:13:13 EST
Sebastian,
Thanks for going through it that closely. You found real errors, not just
wording, so here is what I am doing with each.
The "Measuring" section is wrong and comes out entirely. A wakeup does not
send an IPI to every CPU with a runnable CFS task; it targets one CPU. The
rest of that section reasons from that false premise, so there is nothing
in it worth keeping. Your point that a freshly woken SCHED_OTHER task is
not required to run immediately, and that timer slack and preemption or
interrupt disabled regions add their own jitter, was the useful content
and I did not have it.
The rationale is also wrong. I wrote that lazy exists to cut IPI traffic;
the point is run-to-completion, so that in-kernel work finishes before the
switch and no lock is held across it. I will use your wording for the
model table, including the part about real-time tasks not being delayed.
The tick promotion and the idle-task case are implementation details and
go, and so does the debugfs section, for the reason you gave.
That leaves the four models, runtime selection, the note that this applies
to kernel code only, and /sys/kernel/debug/sched/preempt as another way to
see and change the model.
Both patches are held. If what is left is too thin to be worth a file,
say so and I will drop the series rather than post a trimmed version of
something you did not think should exist.
Quchaosheng