Edition of Thursday 19 November 2026

Sched_ext: A sketch of the scx_lavd scheduler (Part 3)

Comments on “Sched_ext: A sketch of the scx_lavd scheduler (Part 3)”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Changwoo Han of Igalia describes scx_lavd, a Linux CPU scheduler written in BPF on sched_ext that infers task urgency from wait frequency, wake frequency and runtime, then turns it into a virtual deadline, time slice and preemption right. Started for Valve's Steam Deck, it is said to run on the Steam Frame and in Meta's datacenters, though that deployment claim and the quoted figures (futex share, probe costs, code size) are the author's own and unverified. For builders, the design shows how to schedule without annotations.

Read the original at blogs.igalia.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 10 of 144 with a score of 0.68. The panel rated it highest on technical depth (0.97) and new information (0.91), lowest on audience breadth (0.56). Placed No. 10, No. 18 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Deep, detailed technical writeup of an established Linux sched_ext scheduler with real deployment evidence; substantive and novel, though audience is somewhat niche and the excerpt is truncated.
AI judgeJudge 3gpt-5.6-luna
Detailed engineering account of a BPF Linux scheduler spanning gaming, heterogeneous hardware, energy efficiency, datacenter load balancing, and cgroup isolation, with implementation formulas, measurements, and deployment context.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.68total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.63
  • Reader interest0.79
  • Audience breadth0.56
  • Practical relevance0.64
  • Substantiated0.80
  • Technical depth0.97
  • New information0.91
  • Counts against: Promotional0.05
  • Counts against: Overclaim0.15

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.620.450.820.630.37+0.24+0.151
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.670.800.900.790.23+0.26+0.205
Audience breadthHow many people who build technology does it concern?0.600.400.680.560.28+0.13+0.073
Practical relevanceHow useful is it to someone who builds software or tech products?0.540.550.840.640.30+0.22+0.141
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.780.750.880.800.13+0.05+0.040
Technical depthHow technically substantive is it?0.990.920.990.970.07+0.05+0.048
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.900.850.980.910.13+0.05+0.046
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.060.050.040.050.02−0.19−0.010
OverclaimDo the headline or conclusions claim more than the body supports?0.210.150.080.150.13−0.11−0.016
Sum of contributions+0.679
Claim-check penalty0.000
Total, as published0.679

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #10 on Rubric, 19 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-19/10/"><img src="https://rubric.hrih.si/badge/2026-11-19/10.svg" alt="Ranked #10 on Rubric, 19 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 7 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Couldn’t checkNumber

    scx_lavd is now deployed to the Steam Frame VR headset and to Meta's datacenters.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “I am happy to share that scx_lavd is now deployed to the Steam Frame, a VR headset, and to Meta’s datacenters”

    The source says

    No passage could be compared.

    Source cited by the article: lpc.events/event/19/contributions/2099

  2. No source givenNumber

    Since its first commit in the scx repository in March 2024, scx_lavd has grown to about 12,100 lines, 904 commits, and 42 contributors.

    The article gives no link or citation for it.

    The article says

    “Since its first commit in the scx repository in March 2024, it has grown to about 12,100 lines, 904 commits, and 42 contributors”

    The source says

    No source to compare with.

  3. No source givenNumber

    About 80% of system calls in games running on SteamOS were futex, according to the author's strace logs.

    The article gives no link or citation for it.

    The article says

    “About 80% of system calls were futex”

    The source says

    No source to compare with.

  4. No source givenNumber

    About 70-75% of scheduling in a game is initiated by a blocking system call, and only 25-30% by preemption or the timer tick.

    The article gives no link or citation for it.

    The article says

    “About 70-75% of scheduling in a game is initiated by a blocking system call (epoll, pipe_read, futex_wait). Only 25-30% is caused by preemption or the timer tick”

    The source says

    No source to compare with.

  5. No source givenVersion

    sched_ext reached mainline Linux in version 6.12.

    The article gives no link or citation for it.

    The article says

    “sched_ext itself reached mainline in 6.12, more than a year later”

    The source says

    No source to compare with.

  6. No source givenNumber

    Measured per futex operation on an AMD Ryzen 9 PRO 6950H, fentry costs 48 nsec, fexit 76 nsec, and a tracepoint 130 nsec.

    The article gives no link or citation for it.

    The article says

    “fentry costs 48 nsec, fexit 76 nsec, and a tracepoint 130 nsec”

    The source says

    No source to compare with.

  7. No source givenNumber

    On a Snapdragon board, delivering 1024 capacity with the prime core costs 2.33 W, while two performance cores at 512 each cost about 0.41 W, about 5.6× less.

    The article gives no link or citation for it.

    The article says

    “Two performance cores at 512 each deliver the same compute for about 0.41 W in total — about 5.6× less”

    The source says

    No source to compare with.

  8. No source givenDate

    Core compaction landed in LAVD in June 2024.

    The article gives no link or citation for it.

    The article says

    “Core compaction landed in June 2024, and it is where power entered LAVD’s model at all”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 1 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 19 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Sched_ext: A sketch of the scx_lavd scheduler (Part 3)”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.