Overview of the Current Approaches to Enhance the Linux Scheduler
summary
Argues that a power-aware scheduler, driven by per-entity load tracking and using percentage utilization instead of nr_running, actually consolidates threads into power domains so whole sockets can sleep. Implements the policy on two-socket, 8-cores-per-socket x86 and POWER SMT4 machines and tests with ebusy/Kernel-bench: consolidation holds until socket capacity and yields measurable power savings (normalized against default scheduler). Behavior falls back to default when queues deepen; concerns remain about NUMA/cache churn and the need for broad regression testing.
AI-written summary · about
chapters (11)
- 0:00Introduction to Linux scheduler
- 1:30Scheduler goals and architecture
- 4:43Power-aware scheduling concept
- 7:14Load balancing and race to idle
- 11:06Utilization metrics
- 16:42Task behavior analysis
- 21:01Per-entity load tracking
- 27:28Mainline integration challenges
- 30:15Experimental results
- 33:31Future power efficiency efforts
- 35:41Q&A and closing discussion
