3 ms·
I have hard time connecting "machine learning" with what RISC-V is about. Above all, the original plan for RISC-V was to make a barebone MCU ISA first, and eve
by baybal2 7y ago
I have hard time connecting "machine learning" with what RISC-V is about.
Above all, the original plan for RISC-V was to make a barebone MCU ISA first, and everything else second.
This was largely to ARM being very militant with terms on RTL access for M* series cores for commercial use.
If you throw enough extension, and workarounds even on top of 8051, you should be able to make a CPU grade core with it. But you being able to do it, doesn't mean you should.
- brucehoult 7y agoRISC-V was originally developed because some vector-processor / ML people at Berkeley needed an extensible control processor for their specialized hardware. They'd previously been using ancient 32 bit MIPS but they needed 64 bit, a good amount of spare opcode space for custom instructions, and reasonable licensing and nothing suitable existed so they rolled their own. RISC-V with the almost-done Vector extension is likely to be a big force in ML hardware.
- pjmlp 7y agoML hardware has more to gain from FPGAs.
- brucehoult 7y agoBased on what? Whatever number of ALUs / DSP slices you can put in an FPGA and soft-wire together, you can put just as many hard-wired in a custom SoC with lower area and cost, and faster performance. An FPGA is good for prototyping this until you figure out the best arrangement, sure, but three months later you can have real chips.
- pjmlp 7y agoBased on Google's TPUs, and Microsoft's Brainwave.
- monocasa 7y agoTPUs are not FPGAs.
- pjmlp 7y ago> Tensor Processing Units (TPUs) are Google’s custom-developed application-specific integrated circuits (ASICs) used to accelerate machine learning workloads. https://cloud.google.com/tpu/docs/tpus?hl=en https://cloud.google.com/tpu/docs/tpus?hl=en > Project Brainwave is a deep learning platform for real-time AI inference in the cloud and on the edge. A soft Neural Processing Unit (NPU), based on a high-performance field-programmable gate array (FPGA) https://www.microsoft.com/en-us/research/project/project-brainwave/ https://www.microsoft.com/en-us/research/project/project-bra... I got the TPUs wrong and Brainwave right. What they certainly are not is RISC-V.
- nickik 7y agoThe guy who designed TPU works on RISC-V and is a fan of RISC-V. And on of the reason was his experience with TPU, he realizes that custom hardware is really great but a more generally programmable approach would have advantages. That's exactly what the RISC-V Vector extension was designed for. When they started TPU RISC-V wasn't ready for something like that and the Vector extension was at best an idea. Saying 'RISC-V' is bad for ML because XY product doesn't use it, is a terrible argument in general. Over the next 10 years we will have literally 1000s of different things that make AI fast. All of those come with tradeoffs. RISC-V as a base chip for many system is clearly a great fit, even on FPGAs. The RISC-V Vector extension is an excellent for many AI problems and many companies are currently working on that.
- _chris_ 7y agoTo add to what you said, a 64 bit ARM ISA didn’t publicly exist yet when Berkeley started RISC-V.
- pjmlp 7y agoAn 8051 maybe not, but an army of Z80s... https://www.ijcai.org/Proceedings/81-2/Papers/071.pdf https://www.ijcai.org/Proceedings/81-2/Papers/071.pdf
- brucehoult 7y ago100 MIPS and 16 MB of RAM from 256 Z80s in 1981. You can get the same from a single RISC-V soft core in a cheap FPGA board today. More, because a 32 bit RISC MIP is worth several times more than an 8 bit Z80 MIP.
- nickik 7y ago> Above all, the original plan for RISC-V was to make a barebone MCU ISA first, and everything else second. This is simply not correct. RISC-V was designed to allow minimal cores but by design it also tried to cover everything from minimal to HPC. > This was largely to ARM being very militant with terms on RTL access for M* series cores for commercial use. Again this is not correct. Are you just making this stuff up? The reason they developed RISC-V is because of complexity and license issues that would not allow them tape out say x86 or ARM. > If you throw enough extension, and workarounds even on top of 8051, you should be able to make a CPU grade core with it. But you being able to do it, doesn't mean you should. Why not? Is your instruction gone run slower because it spec is written down in a different PDF document? Are you mixing up ISA and micro-architecture? If you take the whole RV64GCVBH you have a full featured core that is designed to allow super high performance implementation. And the ISA design is easily better then any of the other ISAs.