Understanding the Linux Kernel: The Scheduler

·Hacker News··

In the previous article we looked at how the kernel gives every process its own private view of memory. But memory is only half of what a process needs to actually run. The other half is the CPU itself — and there are only so many CPUs in a machine, while there are usually hundreds or thousands of things that want to run on them. So somebody has to decide, constantly, who gets a CPU and for how long. That somebody is the scheduler. Every few milliseconds, on every core, the kernel asks itself t

Read full article →

Related Articles

Should I run plain Docker Compose in production in 2026?
pmig · Hacker News · 2mo ago
Computer Use is 45x more expensive than structured APIs
palashawas · Hacker News · 1mo ago
Bun is being ported from Zig to Rust
SergeAx · Hacker News · 1mo ago
Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem
ozkatz · Hacker News · 1mo ago
RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust
atilimcetin · Hacker News · 1mo ago