3 ms·
> The only complication here would be if they have differing extensions like AVX512 Which they do, Atom tops out at SSE4.2.
by masklinn 6y ago
> The only complication here would be if they have differing extensions like AVX512
Which they do, Atom tops out at SSE4.2.
- chx 6y agoThey can easily disable the differing extensions in the BIG core.
- NullPrefix 6y agoWon't be BIG anymore if it's gimped, will it?
- kllrnohj 6y agoIt will. The performance different between an Intel Atom and a Core i3 has basically nothing to do with differing instruction set extensions. AVX2 support is not why a Core i3 runs circles around an Atom, particularly since the overwhelming majority of instructions executed are not AVX anyway.
- rbanffy 6y agoI'm pretty sure my computer does a lot of AVX while it matches virtual backgrounds to my video feed, or while it tries to figure out voice commands. All that can be done with SSE and probably with x87 instructions, but, still, software will try to pick the best option.
- fluffy87 6y agoBinaries need to target a minimum subset, but can use run time feature detection to query differences. If a binary does that, the OS can just not migrate that binary across cores.
- loeg 6y agoHow would the OS know? The only mechanism I can come up with is to detect illegal instruction traps on small cores, then flag the thread as big-core-only and re-start the execution at the bad instruction. That's not ideal but maybe workable. (If it traps on the big core, too, it's just a bad instruction and SIGILL is raised to userspace like usual.)
- kllrnohj 6y ago> Atom tops out at SSE4.2. SSE itself tops out at 4.2, but Tremont does support the newer SHA extensions. AVX appears to be the only missing thing, but AVX isn't even standard across Intel's other lines, either. The Pentium line doesn't support AVX either, for example, even though they are using Skylake & newer micro-architectures. So you currently can't assume AVX support, and you still won't be able to assume AVX support. Why does this matter?
- loeg 6y ago> Why does this matter? Operating systems move threads between cores. If those cores support different features, threads that are migrated to low-feature cores might experience illegal instruction traps despite correctly checking for instruction features.
- twic 6y agoMaybe standard application code all runs on the big core, and the little cores are like the system assist processors on IBM mainframes - used to run OS jobs or specific application support code, to free up the main processor for other work (or idling). For this to work, there would need to be a small set of undemanding tasks that account for a lot of machine time. Feeding video to the GPU? All sorts of GUI compositing and housekeeping? Handling network connections in the browser? I don't think this is a good explanation, but it's fun to think about.
- Dylan16807 6y agoThat would be pretty disappointing if they can't handle normal processes too. It's easy to end up with a bunch of processes that are using small amounts of CPU but aren't dedicated background tasks. Even just looking at a browser, I might have half a dozen generic tab processes open, each using a small amount of CPU. But then I navigate one to a game, and I want that particular tab to get near-exclusive access to the big core while the others use only the little cores.
- moonchild 6y ago