16 ms·
I'm curious why the Neoverse N1/N2 designers left SMT off of the table? I'd assume that any workload that benefits from 80 cores would benefit from 160-threads
by dragontamer 5y ago
I'm curious why the Neoverse N1/N2 designers left SMT off of the table?
I'd assume that any workload that benefits from 80 cores would benefit from 160-threads (on those 80 cores). Apple's decision to avoid SMT on M1 kinda-sorta makes sense, from the perspective that phones probably don't have throughput-sensitive workloads like servers.
But if databases / other systems with lots of I/O or RAM-heavy wait times start coming up, surely SMT would easily improve performance without much costs in area or power?
---------
It seems like the lower-power E1 core (Efficiency core) has SMT. So the ARM / Neoverse team has the experience to bring SMT should they desire it. This suggests that there's some design reason they left SMT off the table.
The N1/N2 cores are more "general purpose", so I'd assume that they'd see more workloads than E1. If E1 benefits from SMT, why not N1/N2?
- SkyMarshal 5y agoCould it have anything to do with the Portsmash attack against hyperthreaded systems? I'm not current on this one, but I recall when it first came out that disabling hyperthreading was the only solution. Has it been solved yet, or are some chipmakers avoiding enabling hyperthreading now as a result? https://nvd.nist.gov/vuln/detail/CVE-2018-5407 https://nvd.nist.gov/vuln/detail/CVE-2018-5407
- dragontamer 5y agoI doubt it. Otherwise, they would have disabled SMT / Hyperthreading on E1 cores. That's the confusing thing: they have the tech on one core, but not the other.
- twoodfin 5y agoPerhaps the rationale is something like, “If your workload is memory-bandwidth-bound on 80 threads, this system is not for you.” Seems like its ideal workload is lots of compute on a cache-friendly quantity of data.
- dragontamer 5y agoThe opposite. If you hit a memory-bandwidth bound on 80 threads, there's no point going up to 160 threads. In most situations, I expect code to be memory-latency bound on a single thread. (Ex: node = node->next style traversals are quite common, and you cannot progress until the memory has responded). This is exceptionally common in interpreted code (Java, Javascript, PHP, Python), especially OOP-code. So your 80 cores are sitting there waiting for RAM-latency to respond. Wouldn't it be nice if they could execute 80-other-threads in parallel while waiting? This converts a RAM-latency problem into a RAM-bandwidth problem. ------------ ONLY problems that are memory-bandwidth bound on 80 threads will benefit from this architecture.
- rbanffy 5y agoOne of the reasons for SMT is to keep a wide backend occupied. If a single thread plus a reorder buffer and speculative execution can keep the backend busy, there’s no reason to have more threads. OTOH, if your reorder buffer can’t keep your backend full, adding threads may be cheaper in terms of silicon area.
- dragontamer 5y agoYes, your comment makes sense but... The Neoverse E1 is a 2-wide decode core with SMT (wtf??). The Neoverse N1 is a 4-wide decode core (1-thread per 1-core). ------- You're right in that the N1 is narrower than Skylake / Zen. But N1 isn't too shabby: it has 8 execution pipelines: 1 branch, 3x 64-bit integer, 2x 128-bit vector, and 2 load/store. Furthermore: the core that ARM decided to shove their SMT-effort into is the E1, which is probably 1/2 the size of a N1 (well, at least 1/2 sized decode).
- my123 5y agoFor E1, it's because of less aggressive OoO for power saving, and a very aggressive power target of 180mW at 2.5GHz on 7nm. It's within 1.5x of Cortex-A55 perf on single threaded workloads, and with efficiency as the mantra, SMT was worth it there. (but we'll see what happens in future designs... there's both the in-order Cortex-A5xx and the OoO Cortex-A6x which is Neoverse E for the power efficient role)