News for hackers. Stuff that matters.
Re:RISC-V isn’t as interesting as you think by PaulHoule on Tuesday February 02, 2021 @01:13PM (#26004441)
Right, every so often BOOM's Github page gets reposted as if it was something new, and some of the leadership of RISC-V will talk about this architectural feature or that architectural feature that might support a high performance RISC-V chip, but the proof of a high-performance chip is a high-performance chip.

(The experience of Intel's Itanium, IBM's Cell processor and many others shows that it's not enough to have a few good ideas but you have to have ZERO bad ideas that slow you down to get a high performance design.)

Re:RISC-V isn’t as interesting as you think by monocasa on Tuesday February 02, 2021 @02:24PM (#26005364)
I think x86 shows that you don't have to have zero bad ideas in order to get a high performance design.
Re:RISC-V isn’t as interesting as you think by PaulHoule on Tuesday February 02, 2021 @04:10PM (#26006707)
You have to have zero bad ideas that set a ceiling on performance... e.g. you have clear ALL the bottlenecks out of the way.

Just doing something about the one potential bottleneck that you feel like doing something about doesn't necessarily get you a gain in performance at all.

Re:RISC-V isn’t as interesting as you think by monocasa on Tuesday February 02, 2021 @04:26PM (#26006957)
Can you point out the specific bottlenecks that hampered Itanium and Cell?
Re:RISC-V isn’t as interesting as you think by PaulHoule on Tuesday February 02, 2021 @05:06PM (#26007544)
Itanium's problem I know pretty well.

The idea of scheduling parallelism in the compiler (VLIW) doesn't work for mainstream workloads because the time it takes for data to come back from the DRAM is highly variable.

A super-scalar processor can possibly run some instructions at the hardware level while other block wait until data gets back from DRAM.

A VLIW processor packs N instructions together (say N=3) and if one of them is blocked by DRAM, they all block. (If one of them is blocked by Optane they all block for a very long time...)

It looks obvious in retrospect but it's amazing how most of the RISC workstation vendors missed it and put themselves out of business by getting on the Itanic train.

(VLIW is successful for DSP and GPU, but that's because workloads like that can have completely predictable fetches)

I don't know what the problem w/ Cell was exactly, but it was the same in that it couldn't pull data from DRAM fast enough to keep the silicon busy.

Re:RISC-V isn’t as interesting as you think by monocasa on Tuesday February 02, 2021 @05:32PM (#26007914)
With Itanium, they had advanced loads to decouple the pipeline from unknown memory latencies.

Also Itanium was a heavily superscalar design; I think you meant out of order.

Cell just plain didn't really let you directly address main RAM, so you never saw unknown DRAM accesses stalling the cores. Access to the local memory was always single cycle.

In neither case was unknown RAM latencies an issue with the design.