3 ms·
"Rush to idle" is very much a real thing, and a useful thing, and remains a core principle of CPU design and scheduling, however some things tend to keep runnin
by masklinn 5y ago
"Rush to idle" is very much a real thing, and a useful thing, and remains a core principle of CPU design and scheduling, however some things tend to keep running but are pretty cheap e.g. OS background processes which mostly do IO or are semi-actively waiting.
In that case "rush to idle" is not that useful, and waking a big and expensive core (not to mention ramping up its frequency) leads to much higher power consumption for limited gain.
In fact recent big.LITTLE scheduling has been leveraging this: in the oldest model the SoC or kernel would activate either the big or the little cluster[0] depending on what it believed was useful, then the CPU got split "vertically" so the kernel would see each pair of big and little cores as a single vcore, and whichever of the real cores was best for the workload on that vcore would get selected.
More recent big.LITTLE implementations have gone fully heterogenous, if you have 4 small and 4 big cores the system sees and shows 8 actual cores with different performances, and the scheduler tuning selects which tasks go where.
[0] big.LITTLE clusters are the "banks" of respectively big and little cores
- kd913 5y agoDoes it really spin up a big core? AFAIK different C-states dictate that per-core and different caches power on. Given that, surely this can be extended further with ALUs, FPUs etc only being powered on as necessary? I assume that is already the case no? Or is this more towards having smaller denser cores with fewer interconnects and components for even higher power efficiency?