Linux kernel drops UP scheduler in 2025, favoring SMP unification. Learn how this affects legacy single-core systems, benchmark tradeoffs, and why developers call it a necessary evolution for modern hardware
The End of an Era: Single-Core Linux Kernels Face Major Changes
In a move signaling the obsolescence of single-core computing, Linux kernel developers have proposed eliminating the dedicated uniprocessor (UP) scheduler.
A 43-patch series posted by veteran developer Ingo Molnar aims to unify the scheduler around SMP (Symmetric Multi-Processing) logic, simplifying maintenance but adding minor overhead for rare UP users.
Key Changes:
175+ #ifdef CONFIG_SMP blocks removed, reducing code complexity
0.3% kernel size increase for UP builds due to unused SMP logic (e.g., load-balancing)
~5% slower context-switching in benchmarks (
perf bench sched pipe)
Targets modern hardware: Even $20 Intel Celeron and embedded chips now feature multi-core designs
Why This Matters for Developers and Enterprises
1. Code Simplification = Fewer Bugs
The Linux scheduler has accumulated 25 years of divergent UP/SMP paths, causing:
Hidden build failures (under-reported in Git history)
Maintenance burdens for niche UP edge cases
Review complexity with 175 preprocessor conditionals
Ingo Molnar notes:
"The burden of proof now shifts: If you care about UP performance, submit optimization patches."
2. Hardware Reality Check
Embedded systems now default to dual-core+ designs (Raspberry Pi, ARM SoCs)
Cloud/enterprise workloads rely on SMP scalability
Legacy UP use cases are primarily vintage hardware or academic projects
Performance Tradeoffs for Niche Users
| Metric | UP Kernel Before | UP Kernel After | Change |
|---|---|---|---|
| Kernel Size | 28.8MB (text) | 28.9MB (text) | +0.3% |
| Context Switch | 2.55s | 2.69s | +5.3% |
| Maintainability | High complexity | Unified codebase | 175+ #ifdefs removed |
Bottom Line: The 0.3% bloat is a non-issue for modern systems but may impact:
Retro computing enthusiasts
Industrial controllers with UP-only firmware
Research labs using decades-old instrumentation
FAQ: Linux Scheduler Changes
Q: Will my Raspberry Pi 1 (single-core) still work?
A: Yes, but with marginally slower context switches. Most Pi users upgraded to multi-core models years ago.
Q: How does this affect cloud providers?
A: No impact—cloud instances already use SMP kernels.
Q: Can I revert to the old UP scheduler?
A: Only via custom kernel patches, which Molnar discourages due to maintenance costs.
Nenhum comentário:
Postar um comentário