3 ms·
6.6 is the release where process management got real. 1. We can now adjust how much of each cpu a process can use; this pull. Before we could use affinity to e
by jauntywundrkind 3y ago
6.6 is the release where process management got real.
1. We can now adjust how much of each cpu a process can use; this pull. Before we could use affinity to enable or disable core access, but now we can also say, only use a little of this core. Leave most of this core for others. More flexibility in figuring out scheduling plans.
2. Now we can change the boost behavior per core. So we can set one or two or so super boosted cores & keep others a but lower. Then assign work to this high clock rate core or cores.
https://news.ycombinator.com/item?id=37458227 https://news.ycombinator.com/item?id=37458227
3. Now processes will tend to stay next to their l3 cache, whereas before they wouldn't understand that they were moving across l3 cache zones. So now they'll tend to have hitter local caches.
https://news.ycombinator.com/item?id=37458221 https://news.ycombinator.com/item?id=37458221
Major boost to the flexibility of workload handling in 6.6.
- sgt 3y agoSomewhat related; How will this affect (or rather let's say benefit) eBPF?
- jauntywundrkind 3y agoGood question. The sched_ext scheduler seems to be the core place where Meta & Google engineers have explored eBPF based scheduling. It's still being hacked on, ongoingly the initial proposal in November 2022. https://lwn.net/Articles/922405/ https://lwn.net/Articles/922405/ https://github.com/sched-ext/sched_ext https://github.com/sched-ext/sched_ext Ideally we'd see that branch figure out how to incorporate some of these ideas. I haven't done an analysis to explore. The article mentions one sample eBPF scheduler that does some cgroup work, but I haven't looked deeper.