4 ms·
1. CPUs are about minimizing latency. CPUs aren't designed to scale, they're designed to execute your (presumably single-threaded) program as quickly as possib
by dragontamer 7y ago
1. CPUs are about minimizing latency. CPUs aren't designed to scale, they're designed to execute your (presumably single-threaded) program as quickly as possible. This means speculatively executing "if" statements and speculatively predicting loops, renaming registers and more.
2. GPUs are the scalable architecture: The 2080 Ti has 4352+ SIMD cores (136 compute units). And NVidia can load 30+ threads per compute unit, so 130560+ conceptual threads (kinda like hyperthreading) can exist on a GPU executing at once.
3. VLIW seems like a dead end. AMD GPUs gave up the VLIW instruction set back in 2008. Instead, the SIMT AMD GCN or NVidia PTX model has been proven to be easier to program, easier to schedule, and easier to scale. If you want high-scaling, you should do SIMD or SIMT, not VLIW. Intel, RISC, ARM, and Power9 have all chosen SIMD for scaling (AVX, ARM-SVE, Power9 Vector Extensions, NVidia PTX, and AMD GCN).
4. I think VLIW might have an opportunity for power-efficient compute. Branch-prediction and Out-of-order execution of modern CPUs relies on Tomasulo's algorithm + speculation, which feels like it wastes energy (in my brain anyway). VLIW would bundle instructions together and require less scheduler / reordering overhead. If a company pushed VLIW as a power-efficient CPU design... I think I'd believe them. But VLIW just seems like it'd be too unscalable compared to SIMD or SIMT.
5. Can we stop talking about RISC vs CISC? Today's debate is CPU (latency-optimized) vs GPU (bandwidth-optimized). The most important point is both latency-optimized and bandwidth-optimized machines are important. EDIT: Deciding whether or not a particular algorithm (or program) is better in latency-optimized computers vs bandwidth-optimized computers is the real question.
- atq2119 7y agoAll good points, but: > VLIW seems like a dead end. Since you mentioned this in the same breath as GPUs, I feel I have to point out that according to some reverse engineering paper, Nvidia's Turing is a VLIW architecture. (I'm talking about the actual hardware here, not PTX.) Presumably they have some reason for that that's unrelated to increasing IPC, since AFAIK their GPUs aren't superscalar.
- dragontamer 7y ago> Since you mentioned this in the same breath as GPUs, I feel I have to point out that according to some reverse engineering paper, Nvidia's Turing is a VLIW architecture. (I'm talking about the actual hardware here, not PTX.) NVidia Volta / Turing has been reverse engineered here: https://arxiv.org/abs/1804.06826 https://arxiv.org/abs/1804.06826 . EDIT: I'm talking about the actual hardware, the SASS assembly, not PTX. It doesn't look like a VLIW architecture to me. Page 14 for the specific instruction-set details. I realize this is mostly a matter of opinion, but... those control-codes are very different from the VLIW that was implemented in the Itanium. > On Volta, a single 128-bit word contains one instruction together with thecontrol information associated to that instruction. So NVidia has a 128-bit instruction (16-bytes) with a LOT of control information involved. The control information encodes read/write barriers, but there is still one-instruction per... instruction. The "core" of VLIW was to encode more than one instruction-per-bundle. Itanium would encode maybe 3-instructions per bundle for example. What NVidia is doing here is having the compiler figure out a bunch of read/write/dependency barriers so that the GPU won't have to figure it out on its own (I presume this increases power-efficiency). The only thing similar to VLIW is that NVidia has a "complicated assembler" which needs to figure out this information and encode it into the instruction stream. Otherwise, it is clearly NOT a VLIW architecture. > Presumably they have some reason for that that's unrelated to increasing IPC, since AFAIK their GPUs aren't superscalar. NVidia Turing can execute floating-point instructions simultaneously with integer-instructions. So they are now superscalar. The theory is that floating-point units will be busy doing the typical GPU math. Integer-instructions are primarily used for branching / looping constructs (and not much else in graphics-heavy code), so they are usually independent operations.
- brandmeyer 7y ago> VLIW seems like a dead end. VLIW has been amazingly successful in DSP. All the world's baseband processors use VLIW machines. Many of the accelerated video decoders are also VLIW machines under the covers.
- dragontamer 7y agoWhile I recognize that DSPs are power-efficiency champs, I'm not aware of any DSP (or VLIW architecture) being used in top supercomputing lists, like TOP500 or GREEN500. Its all CPU-based, GPU-based, or that weird "PEZY" from Japan (which is just... weird). Who knows what the future holds... but SIMD is currently making a big change to the supercomputing landscape (both in CPU-design with AVX512 and GPU-design with NVidia).
- brandmeyer 7y agoI'm pretty sure that's because they are hard to program for. Although automatic compilers and instruction schedulers for VLIW machines exist, they aren't nearly as good as hand-tuning. VLIW machines have a niche where a fairly small amount of code is both very arithmetic-intensive, predictable, and executed in a power-sensitive environment. In HPC and most business workloads, you just can't dedicate the labor required to making your code work well on them.
- marcosdumay 7y ago> I think VLIW might have an opportunity for power-efficient compute. Well, I think if such advantage is real, it leads to taking over the servers, HPC, and obviously, mobile. I imagine some hybrid approach will wind in the end. I do expect transparent graph processors to come from VLIW with real time optimization done by software, OoO style. This combo feels unbeatable, but all the real problems hide in the details anyway.
- dragontamer 7y agoFrom my understanding, Mobile chips have VLIW DSP chips in them still. So it seems like VLIW designs they have some advantage in minimizing energy usage. Qualcomm Hexagon (aka: Snapdragon 855) is still used for a lot of mobile applications, and its definitely a VLIW architecture. http://pages.cs.wisc.edu/~danav/pubs/qcom/hexagon_hotchips2013.pdf http://pages.cs.wisc.edu/~danav/pubs/qcom/hexagon_hotchips20... But VLIW isn't popular anywhere else by my understanding.