4 ms·
The RISC-V activity is very interesting. I particularly love that they did a 1.4GHz core on 48nm SOI and are working on 28nm level. This knocks out some of the
by nickpsecurity 11y ago
The RISC-V activity is very interesting. I particularly love that they did a 1.4GHz core on 48nm SOI and are working on 28nm level. This knocks out some of the early, hard work of getting competitive hardware at an advanced process node. I'd like to see two things in this work: microprogrammed variant with an assembly or HLL to microcode compiler; tagged variant like SAFE/CHERI processors with IO/MMU that seemlessly adds & removes tags during DMA. That would be way better for security-critical applications than most of what's out there. Multi-core would help, too.
Meanwhile, Gaisler's SPARC cores are commercial, open-source, customizable, support up to 4 cores in Leon4, integrated with most necessary I.P., and can leverage the SPARC ecosystem. Anyone trying to do an open processor can get quite the head-start with that. A few academic and commercial works are already using it. Plus, the SPARC architecture is open as such that you only pay around $100 for the right to use its name.
So, Gaisler's SPARC cores with eASIC's Nextreme seems to be the best way to rapidly get something going. The long-term bet is RISC-V and they could do well copying Gaisler's easy customization strategy. Might be doing that already with their CPU generator, etc: I just read the Rocket paper so far. The solutions built with one can include a way to transition to the other over time.
- asb 11y agoYou might be interested in our (lowRISC's) tagged memory implementation. We describe our planned approach in http://www.lowrisc.org/docs/memo-2014-001-tagged-memory-and-minion-cores/ http://www.lowrisc.org/docs/memo-2014-001-tagged-memory-and-... My colleague Wei gave an update at the workshop a couple of weeks ago http://riscv.org/workshop-jun2015/riscv-tagged-mem-workshop-june2015.pdf http://riscv.org/workshop-jun2015/riscv-tagged-mem-workshop-...
- ChuckMcM 11y agoIt would be great if you also implement ECC. Memory tagging is only as good as you can trust the memory you are tagging.
- microcolonel 11y agoSee: rowhammer. ;-)
- minthd 11y agoeAsic is only using it's eBeam direct-write technology(which is great for prototype development for cheap) for 90nm chips. So maybe using 14nm FPGA's is better.
- nickpsecurity 11y agoNextreme 1 is 90nm, Nextreme 2 is 45nm and Nextreme 3 is 28nm. Their easicopy service mentions all three. So, am I missing something? Or can't you just put a Gaisler SPARC design on an arbitrary Nextreme for S-ASIC benefits and convert it to ASIC later when cash is available? Note: Gaisler's LEON3 and LEON4 are listed in their I.P. library list for Nextreme devices. Note 2: Avoiding FPGA's except in early stage due to high unit costs and energy use. My favorite, though, are the Achronix Speedsters and their asynchronous circuits. Badass. They'll get bought out, though. (sighs)
- hga 11y agoIntel bought Altera; the are or were doing fab work for Achronix, which they invested in as well.
- nickpsecurity 11y agoThe Intel and Altera combination is especially exciting. The first time I got to see the real potential of FPGA's in practice was when SGI added them to NUMA machines. The onboard memory and interconnect meant no huge slowdown for going through PCI bottleneck. A FPGA fabric as a layer of a high-end, Intel chip with software & FPGA cooperation using on-chip interconnect would kill everything else in performance. The only thing better might be one of the POWER chips with a FPGA. Maybe IBM should buy Xilinx or Achronix... mwahahaha. I'll probably be able to afford Intel's, though, unlike IBM's. ;)
- minthd 11y agoWhile all eAsics are via programmable , only the 90nm version is programmable by eBeam. the rest requires a mask and minimum volumes - ie large expense. sorry on mobile so no link. So maybe building something on(the gaisler is a good idea) an FPGA ,and proving enough market value and finding customers (not easy) ,should be the first part , and only than , using eAsic or Fujitsu's similar service for mid-volume ?