3 ms·
The A64Fx really is something between a CPU and a GPU, if we're being fair.
by sudosysgen 6y ago
The A64Fx really is something between a CPU and a GPU, if we're being fair.
- dragontamer 6y agoThe only GPU-like thing it has is on-board HBM2 RAM (which other CPUs could do, but haven't bothered to do for some reason. Except that one Xeon Phi using the HMC competitor to HBM). The SIMD-model of A64Fx: the SVE instruction set of ARM, is coming to mainstream Neoverse V-series ARM chips within a year or two. SVE is CPU-parallelism. Well, its SIMD, but its just 512-bit SIMD (equivalent to AVX512 in width). So that's smaller scale SIMD / CPU parallelism IMO. Those A64Fx are going to be branch-predicting and executing those SIMD-instructions out-of-order. Its a CPU. ------- I consider GPUs to be the simpler in-order but more parallel stuff (AMD, NVidia, Xilinx maybe). But you're right in that the line keeps getting blurred each year. (NVidia's dual-issue pipelines is a very CPU-like feature. AVX512 and SVE pushing 512-bits is getting closer-and-closer to GPU-like SIMD widths)
- sudosysgen 6y agoGPUs can now basically do out-of-order execution using dynamic warp formation and driver-based prediction and optimization. Branch prediction is useless in massively parallel workflows, because of linearization. GPU SIMD is also more complicated than full-SIMD. Nowadays with work-stealing and multiple workgroups, you can have very similar performance characteristics to parallel SIMD on CPUs, just with more perfromance. And in any case, OOE for SIMD instructions loses a lot of it's usefulness on many workflows.
- dragontamer 6y ago> GPUs can now basically do out-of-order execution using dynamic warp formation and driver-based prediction and optimization. That's... not OOE. If you have: add [eax], ebx add ecx, edx A CPU can execute "add ecx, edx" before the "add [eax], ebx" (especially if the [eax] memory read/write is far away: like in DDR4 or worse). A GPU will ALWAYS execute the 1st line before the 2nd line. Dynamic warp formation means that SIMD-lanes can split-up in your warp, but none of the warp is executing anything out-of-order. > Branch prediction is useless in massively parallel workflows, because of linearization. Stockfish NNUE argues otherwise. Only part of the network updates at any given time. Its a massively-parallel problem, but you need dynamic / branch prediction to see which parts of the Neural-Net are actually updating. The idea of CPU-designed networks (Neural Nets that PARTIALLY update, instead of a GPU-network that updates entirely) is intriguing to me. There might be other situations where branch prediction is helpful in other largely parallel problems. ---------- > And in any case, OOE for SIMD instructions loses a lot of it's usefulness on many workflows. More like the SIMD offers enough parallelism to saturate the machine. But NNUE really shows where OOE / branch prediction can suddenly become unexpectedly helpful. Classic SIMD algorithms do not account for branch prediction / OOE benefits. The very existence of high-speed SIMD + OOE + branch prediction is an unexplored part of computer science IMO.
- rrss 6y agoThe A64fx also has hardware synchronization barriers to synchronize cores, which is a pretty GPU-like thing (at least it is very common on GPUs, and rare on CPUs). https://github.com/fujitsu/A64FX/blob/master/doc/A64FX_Specification_HPC_Extension_v1_EN.pdf https://github.com/fujitsu/A64FX/blob/master/doc/A64FX_Speci...