The key point is that the cores are otherwise the same so you don't have the weird intel situation where the e-cores don't support the same instructions as the p-cores.
Intel didn’t have this problem. They simply disabled instructions available on P and not on E. They did face the scheduling issues inherent in heterogenous systems. But so will AMD.
I read somewhere that part of what makes the iOS experience better is tight control over how much CPU background jobs can steal.
systemctl set-property system.slice AllowedCPUs=16-19
Would set the "system" slice to certain pinned cores, but there's nothing automatic.Not the friendliest mechanism for defining what runs on what but it's what I use to make sure that server software I really want on the P cores stays on the P cores.
> We don't know yet what types of cores these new Zen 5 core clusters will have. Half of Zen 5's core count could be dedicated entirely to Zen 5c efficiency cores, or the entire stack could be vanilla Zen 5 performance cores. It could be a mix of both since AMD's slides suggest that there will be different models featuring FP-512 support and some models with low-power cores.