A report from the LPC sched_ext microconference
The Linux Plumbers Conference blog has a report from the sched_ext microconference held in Prague.
Why am I seeing this Ranked on source trust — LWN
It ranks mainly on source trust: LWN is the most reliable outlet we track on this subject, and is the only one on the story so far.
Single-sourced. No second organisation has confirmed it yet.
Link-outLink-out, because only one organisation carries it and no first-party source is on it and the subject could not be identified from the text. Link-out means we point at the publisher and say nothing of our own.
| Factor | Weight | Score | Contribution | Where it came from |
|---|---|---|---|---|
| Corroboration | 0.35 | 0.39 | +0.135 32% | 1 independent org on the story. Tier-3 aggregators never corroborate — they can show something is circulating, never that it is true. |
| Source trustleads | 0.25 | 0.85 | +0.212 50% | LWN is the highest-trust source on this story. Trust is taken from the best source, not averaged. |
| Pickup rate | 0.20 | 0.00 | +0.000 0% | One counted organisation, so there is no spread to measure — nothing has picked this up to set a rate. |
| Freshness | 0.20 | 0.37 | +0.073 17% | Halves every 10 hours from the newest item on the story. This is the only factor that rewards a story for nothing more than being recent. |
Corroboration counts distinct organisations, once each, and only from tiers 1 and 2. Freshness halves every 10 hours, so this ranking is a snapshot and will differ at the next build.
Kuzux · CC BY-SA 2.5 · Wikimedia Commons · illustrativeThe sched_ext microconference at Linux Plumbers Conference in Prague addressed three core areas for the scheduler extension framework. Priority inversion emerged as a central concern, with discussions focused on lock holder and lock waiter preemption, time slice extension, and integrating proxy execution with BPF schedulers. These topics represent ongoing challenges in making sched_ext handle complex scheduling scenarios reliably.
Paravirtualized scheduling was explored as a way to coordinate host and guest schedulers across virtual machine boundaries. The framework would use sched_ext as the policy engine running on the host system, enabling better cooperation between layers. This approach aims to improve scheduling decisions when VMs are involved.
Hardware-aware scheduling capabilities were discussed, leveraging Intel HFI and other hardware feedback mechanisms alongside device and accelerator locality. The goal is to use cache topology and device proximity information to guide task placement decisions. This work targets better performance by aligning tasks with available hardware resources.
What happened
The Linux Plumbers Conference blog has a report from the sched_ext microconference held in Prague. Three main topics dominated the discussions Priority inversion and how to handle it in sched_ext: lock holder and lock waiter preemption, time slice extension, and making proxy execution work together with BPF schedulers. Paravirtualized scheduling: letting the host and guest schedulers cooperate across the VM boundary, with sched_ext as the policy engine on the host. Device and topology-aware scheduling: using hardware feedback (Intel HFI), device/accelerator locality and cache topology to drive task placement.
How this story arrived
Ordered by when each source was first observed, which is what the velocity figure is computed from. Publishers backdate; observed order does not.
- 01 Lwn first seen A report from the LPC sched_ext microconference
Overclock clusters coverage from independent sources and grades it automatically. The figures above are computed, not editorial. This page summarises and links to reporting by the outlets named — follow the links for the original work.