From 87d528b00ad9688acb9dafd7cdb345d61440bffe Mon Sep 17 00:00:00 2001 From: japabu Date: Wed, 28 Oct 2026 13:53:25 +0100 Subject: [PATCH] issues: the placement starvation refuses on main too, 1 of 12 base boots diag3's base2 boot, main 544f9cc3c with #1074's measurement counters, refused wake.onto_busy's partner 7. Every benchcase boot of #1074's sessions and diagnostic sessions is counted: 1 of 12 on main against 3 of 14 on #1074's images, one-sided Fisher exact p = 0.36. Co-Authored-By: Claude Opus 5.5 --- ...lding-parked-threads-for-seconds-at-boot.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/issues/a-spawn-can-miss-a-cpu-holding-parked-threads-for-seconds-at-boot.md b/issues/a-spawn-can-miss-a-cpu-holding-parked-threads-for-seconds-at-boot.md index 33242f61000..e625e3a0bfb 100644 --- a/issues/a-spawn-can-miss-a-cpu-holding-parked-threads-for-seconds-at-boot.md +++ b/issues/a-spawn-can-miss-a-cpu-holding-parked-threads-for-seconds-at-boot.md @@ -11,8 +11,8 @@ partner threads on one CPU, where each partner parks. `place::spawn_on` spawns threads until one first runs on that CPU, with a 5 s budget per partner. The rows that measured took 32–63 ms. In some T14 `benchcase` boots the row instead ran for seconds, inside about 22.7–29.0 s of boot, -the span in which netstack's DHCP lease and `ready` line also land. Three -rows refused, for example "partner_33_was_not_placed: +the span in which netstack's DHCP lease and `ready` line also land. Four +rows refused, one of them on main, for example "partner_33_was_not_placed: 138904_threads_started_in_5s_and_none_first_ran_where_it_was_wanted", and `osbench_sched` exited 1. @@ -20,12 +20,14 @@ T14 `benchcase` boots, all on 2026-10-28: | images | boots | refused | slow but measured | |---|---|---|---| -| main `544f9cc3c`: PR #1074's session 1 base-bench, sessions 3–5 base1/base2, and the diagnostic base image | 8 | 0 | 1: session 4 base2's row ran 23.156–27.025 s (3.87 s), around netstack's `ready` at 24.99 s | -| PR #1074's heads: session 1 head-bench (`1f828f331`), session 2 p1 (`46848c491`), sessions 3 (`5e0cb52b0`), 4 (`cd42d13a4`) and 5 (`0a48bf8b4`) head1/head2, and the diagnostic images at `cd42d13a4` and `0a48bf8b4` | 10 | 3: session 2 p1 (23.963–28.967 s), session 5 head1 (22.705–27.710 s), the `0a48bf8b4` diagnostic image (22.802–27.803 s) | — | - -The slow row happens on `544f9cc3c`, so the behaviour predates #1074. Whether -#1074 raises the refusal rate is not established: 0 of 8 against 3 of 10, -one-sided Fisher exact p = 0.15. The readbacks are PR #1074's sessions 1–5. +| main `544f9cc3c`: PR #1074's session 1 base-bench, sessions 3–5 base1/base2, and its diagnostic base image (`544f9cc3c` with measurement counters) in the first diagnostic session and diag2 and diag3 base1/base2 | 12 | 1: diag3 base2 (23.362–28.364 s) | 1: session 4 base2's row ran 23.156–27.025 s (3.87 s), around netstack's `ready` at 24.99 s | +| PR #1074's heads: session 1 head-bench (`1f828f331`), session 2 p1 (`46848c491`), sessions 3 (`5e0cb52b0`), 4 (`cd42d13a4`) and 5 (`0a48bf8b4`) head1/head2, and its diagnostic images: `cd42d13a4`, `0a48bf8b4`'s merge, diag2's pool1/pool2 and diag3's skew1/skew2 | 14 | 3: session 2 p1 (23.963–28.967 s), session 5 head1 (22.705–27.710 s), the `0a48bf8b4` merge image (22.802–27.803 s) | — | + +Main `544f9cc3c` refuses too, so the behaviour predates #1074. Whether #1074 +raises the refusal rate is not established: 1 of 12 against 3 of 14, +one-sided Fisher exact p = 0.36. The readbacks are PR #1074's sessions 1–5 +and its diagnostic sessions 1–3. diag2's first base2 attempt is left out: +that boot never came back, because the I219 was left in ULP. **What could cause it.** `placement` (`kernel/src/sched/driver.rs`) picks a global rotating start, and `CpuHandles::place` (`kernel/pure/sched/cpu.rs`)