4 ms·
Once when I was much younger first encountering NUMA I came across a bit of code that always did a few magical things with the first physical CPU. We had a fair
by xyzzy_plugh 4y ago
Once when I was much younger first encountering NUMA I came across a bit of code that always did a few magical things with the first physical CPU. We had a fairly elaborate hardware configuration and several peripherals were bound to the first core.
Ever since, when I do any sort of CPU or core pinning or grouping, I leave the first core or two alone if possible. It's convenient to say the first two cores are for all the ancillary stuff, but the last 30 are for our workload.
Now I realize why I never witnessed something like this in all benchmarks I performed... I always ignore the first CPU core.
- anonymousiam 4y agoSmart move! I've always known about core 0 and IRQ processing, but this article introduced me to new dangers (under Linux) associated with core 1. Love your user name too! Plover! Zorton!
- masklinn 4y agoDoes that work with the recent moves to asymmetric cores? Do they set the E cores as the first cores of a socket?
- formerly_proven 4y agoNo, P cores are first, then E cores, at least on ADL.