3 ms·
The author isn't aware apparently of over a decade of work done in FPGA/CPU integration. Both in more sequential languages like System C[1] or in extended instr
by ChuckMcM 8y ago
The author isn't aware apparently of over a decade of work done in FPGA/CPU integration. Both in more sequential languages like System C[1] or in extended instruction set computing like the Stretch[2]. Not to mention the Zynq[3] series where the CPU is right there next to the FPGA fabric.
For "classic" CPUs (aka x86 cpus with a proprietary frontside bus and southbridge bus) it can be challenging to work an FPGA into the flow. But the problem was pretty clear in 2007 in this Altera whitepaper[4] where they postulate that not keeping up with Moore's law means you probably end up specializing the hardware for different workloads.
The tricky bit on these systems is how much effort/time it takes to move data and context between the "main" CPU and the FPGA and then back again (Amdahl's law basically). When the cost of moving the data around is less than the scaling benefit of designing a circuit to do the specific computation, then adding an FPGA is a winning move.
[1] https://www.xilinx.com/products/design-tools/vivado/prod-advantage/rtl-synthesize.html https://www.xilinx.com/products/design-tools/vivado/prod-adv...
[2] http://www.stretchinc.com/index.php http://www.stretchinc.com/index.php
[3] https://www.xilinx.com/products/silicon-devices/soc/zynq-ultrascale-mpsoc.html https://www.xilinx.com/products/silicon-devices/soc/zynq-ult...
[4] https://www.intel.com/content/dam/altera-www/global/en_US/pdfs/literature/wp/wp-01029.pdf https://www.intel.com/content/dam/altera-www/global/en_US/pd...
- blacksmythe 8y ago>> The tricky bit on these systems is how much effort/time it takes >> to move data and context between the "main" CPU and the FPGA and then back again The sweet spot for FPGAs is when the data is streaming. You can build hardware where the data is passed from one stage to another, and doesn't go to RAM at all. Particularly where the data is coming in fast, but with low resolution (huge FPGA advantage for fixed point instead of floating point). FGPAs are much more efficient for signal processing from data collected from an A/D converter (e.g. software defined radio) or initial video processing from an image sensor.
- tomnipotent 8y ago> The sweet spot for FPGAs is when the data is streaming Netezza does this with their hardware, I've been dreaming of the day I could DIY and put a OSS RDBMS on top.
- nickpsecurity 8y agoYeah, the High-Level Synthesis work goes back to the 1990's. Wikipedia has a nice list: https://en.wikipedia.org/wiki/High-level_synthesis https://en.wikipedia.org/wiki/High-level_synthesis They didn't really pan out in terms of large uptake. They did solve some problems pretty well with shorter, developer time. There's also been open source ones designed. Here's a few: http://legup.eecg.utoronto.ca http://legup.eecg.utoronto.ca https://www.synflow.com https://www.synflow.com Many of the other ones seem dead or don't have a software page. I'm not sure what's current in FOSS HLS with C-like languages. Anyone know of other developments at least as good as the two I linked?
- fulafel 8y agoNitpick: LegUp is published under a "no commercial use" license. Synflow mentions they use a "open-source language" but it is not clear how much of the tool chain is open source.
- nickpsecurity 8y agoDidn't know about LegUp restriction. Thanks!