Re: [PATCH v5 13/29] sched/deadline: Keep departing bandwidth across a root domain rebuild
From: Mathieu Desnoyers
Date: Wed Nov 11 2026 - 15:02:56 EST
On 2026-11-11 11:19, Peter Zijlstra wrote:
On Wed, Nov 11, 2026 at 10:35:17AM -0500, Mathieu Desnoyers wrote:
Measured in a 64-vCPU guest with sleeping deadline tasks:
tasks today: rebuild, longest irqs-off single list, all irqs-off
1000 0.75ms, under 0.1ms 0.12ms (0.19ms worst)
10000 7.4ms, under 0.1ms (0.3ms once) 0.9ms (1.2ms worst)
The rebuild itself is 8 times shorter. That comes from updating the
extra_bw of the CPUs once per root domain, not once per task. But the
longest section with interrupts disabled grows with the number of
deadline tasks. I do not think that is a step forward for a real-time
class.
This is domain rebuild? Do we really care about performance there?
My worry is not performance, but rather the contribution of this
"iteration on all tasks" on the irqoff latency of the system, which
is relevant for RT.
What I don't know:
1) is 10k deadline tasks something that we should consider as realistic
for sched deadline, or it's way beyond practical scale ?
2) is a irqoff latency of 1.2ms (rather than 0.3ms) something which is
relevant in terms of irq off latency on a preempt rt kernel, or is it
in the noise ?
3) are those domain rebuild expected to happen with a live RT workload,
or are those operations expected to never happen on a RT system under
real-time constraints ?
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com