21 ms·
<many years ago> when Intel acquired Altera, and announced Xeon CPUs with on-chip FPGAs, I was optimistic that eventually they would add FPGAs to more low-end d
by phendrenad2 6y ago
<many years ago> when Intel acquired Altera, and announced Xeon CPUs with on-chip FPGAs, I was optimistic that eventually they would add FPGAs to more low-end desktop CPUs (or at least Xeons in the sub-$1000 zone). But it never materialized. I'm slightly optimistic this time around too, but I suspect that the fact that Intel didn't do it hints at some fundamental difficulty.
- baybal2 6y agoOn-package, not on-chip
- saddlerustle 6y agoThey never ended up shipping the high end ones either.
- QuixoticQuibit 6y agoIm skeptical as well. The primary reason IMO is the software. How do you easily reconfigure your FPGA to efficiently run whatever computationally intensive and/or specialized algorithm you have?
- SSLy 6y agoMy armchair amateur brain immediately thought about something CUDA-like.
- numpad0 6y agoFPGA code takes hours to compile, yet product/model specific
- FPGAhacker 6y agoYou would use precompiled modules or compositions of these modules (pipeline or parallel). This can be a relatively fast operation. Seconds or less depending on complexity.
- simias 6y agoYou're not wrong but I expect they'd make it so that the various models would be similar enough (at least within a given CPU generation) so that you could use mostly precompiled artifacts instead of rerouting everything from scratch. I've always been pretty skeptical of their approach though, in order to be usable they'd need excellent tooling to support the feature, and if there's one thing that existing FPGA software isn't it's "excellent". Getting FPGAs to perform well is often an art more than a science ("hey guys, let's try a different seed to see if we get better timings") so the idea that non-hardware people would start to routinely generate FPGA bitstreams for their projects is so implausible that it's almost comical to me. Maybe one day we'll have a GCC/LLVM for FPGAs and it'll be a different story.
- pclmulqdq 6y agoBeyond the GCC/LLVM, you also really need a standard library. Nobody is talking about that. Today, if you want a std::map on an FPGA, you have to either pay $100k or build it yourself. That's untenable.
- Someone 6y agoAlso, for the way most modern CPUs are used: how do you task switch? If the hardware is large enough, you can deploy multiple configurations at a time, but does software support that? Is is possible to have relocatable configurations? In theory, you could even page out code, but I guess the speed of that will be slow. Also, paging in probably would be challenging because the logical units aren’t uniform (if only because not all of them will be connected to external wires)
- rjsw 6y agoYou can reconfigure just part of the FPGA, it isn't used all that often though.
- varispeed 6y agoThis can be used with a client-server model, that is if there are enough free cells and I/O available on FPGA it could let it install the configuration and then any application could communicate with it concurrently, maybe with some basic auth.
- Someone 6y agoBut from what I understand of FPGAs, fragmentation would be a serious issue. You may have the free cells and I/O you need to implement some circuit, but if they’re dispersed over your FPGA or even connected, but in the wrong shape for the circuit you’re building, that’s useless. An enormous crossbar could solve that, but I would think that would be way too costly, if practically possible at all.
- threatripper 6y agoI would see it being used more like a GPU than a CPU.
- gmueckl 6y agoEven GPUs multitask all the time, even though it's less obvious. Cooperative multitasking in this context means setting up and executing different shaders/kernels. The overhead involved in this is quite manageable. Repurposing FPGAs to different tasks means loading a new bitstream into the device every time. So it is much more efficient to grant exclusive access to each user of the device for long stretches od time. The proper pattern for that is more like a job queue.
- dragontamer 6y agoAn actual GPU or CPU will always run circles around an FPGA CPU or FPGA GPU. Where FPGAs win are new architectures, like Systolic engines. Entirely different computer designs from the ground up.
- nomercy400 6y agoIt is doable. I've seen it during my Computer Engineering courses 14 years ago. Basically you analyze the code for candidates, select a candidate, upload your custom hardware design, run your operation on the hardware, and repeat. The difficult part is that uploading your hardware to FPGA is in the order of tenths of seconds, which is ages when compared to the nano and micro seconds your CPU works. So your specific operation must be worthwhile to upload. A bit of FPGA on your CPU makes it more flexible, for example your could set a profile such as 'crypto' or 'video' to add some specific hardware acceleration to you general purpose CPU. Imagine your CPU being able to switch your embedded GPU into another CPU core.
- hajile 6y agoCodecs are a great example. Let's say the current zen 2 had an FPGA onboard. AMD could sell you an upgraded design with AV1 support for a few dollars. Most people aren't going to buy a new CPU on the basis of a video decoder, but they'll buy an upgrade to the chip that auto "installs" itself. That's a sale AMD otherwise wouldn't have made.
- wtetzner 6y agoI believe there is some amount of support in OpenCL for FPGAs. If only we could get companies to property support OpenCL, we'd have a nice software interface to pretty much any kind of compute resource on a machine.
- eganist 6y agoI'm optimistic... not so much because of the merits of the acquisition but moreso because of AMD's history with strategic actions. ATI kept them afloat through a CPU performance drought, and divesting globalfoundries secured necessary liquidity. These two alone essentially saved AMD, so I've got faith in leadership being able to make the appropriate strategic maneuvers. But maybe I'm being overly optimistic. (Probably because—disclosure—I'm long AMD. Been long for years.)
- eqvinox 6y agoI'm hoping/expecting a chip that goes into the Epyc/SP3 socket and has the memory & PCIe & socket crossconnect as hard IP but the CPU cores replaced with programmable logic. If you have a use case for FPGAs, it's more likely you want it in a concentrated form like this... not on low-end or desktop systems :/ If I remember correctly, there was something similar back in the early HyperTransport days...
- hderms 6y agoAre you envisioning retaining at least a few cores? It seems like you'd probably still want an OS running on native silicon.
- detaro 6y agoI assume they are thinking about a design for multi-socket systems.
- eqvinox 6y agoYeah I think it's both more effective and cheaper to have dual/quad socket systems with 1 "normal" CPU and the rest filled with FPGAs without CPU cores, just to max out on the raw crunching ability. The PCIe block on the FPGA chips could be flexible enough to (re-?)wire directly into the programmable logic, maybe even reconfigurable to other protocols (e.g. 100GE). Also in "normal" NUMA fashion each FPGA would have the memory channels associated with that socket (presumably through the interconnect as if it were a CPU, so the CPU can access it too.) I'm just looking at this from a logical chain of "who needs FPGAs in their computers?" => "cases with loooots of specific data crunching" => "want a controlling/driving CPU for the complicated parts, but then just concentrate as much FPGA in as possible." => Multi-socket with 1 CPU & rest FPGAs. (There currently is no commodity Quad-socket SP3 mainboard, not sure if this is a design limitation or just no one made one yet? I'd still say the approach works great with only 2 sockets.)
- zrm 6y agoI wouldn't expect to see anything like this on SP3 anyway, since it would take some time to do the work and by then the current generation would likely be whatever they replace SP3 with in order to support DDR5.
- Nokinside 6y agoNokia designed their ReefShark 5G SoC chipset with significant FPGA component and used Intel as their supplier. Intel couldn't deliver what they promised. It was complete disaster. They had to redesign ReefShark and cancel dividends. It was a huge setback.
- noki_throway 6y agoThis is utter bullshit. Nokia f*cked up because they over-engineered their FPGA solution for 5G. They took largest FPGA in the market and couldn't squeeze their design in it. It was not Nokia SoC just plain Stratix10. They moved to own SoC after that glorious project.
- whereistimbo 6y agoYou create a new throwaway account 4 hrs ago just to post this reply?
- whereistimbo 6y agoSo it's Nokia that Charlie @ Semiaccurate was talking about back in 2018 saying that Intel crushed a USD 20bn market cap company https://semiaccurate.com/2018/07/02/intel-custom-foundrys-10nm-meltdown-is-crushing-a-20b-market-cap-tech-giant/ https://semiaccurate.com/2018/07/02/intel-custom-foundrys-10...
- rathel 6y agoApparently after Altera acquisition they sought "synergies" in all the different divisions. My friend was an intern who was tasked with porting some of the network protocol stack to SystemVerilog. Apparently it did work and SystemVerilog was the right HDL to use because of support for structs that can map to packet headers. I'm not sure it's being used in production. It'd be interesting to see how AMD will execute and integrate this acquisition, considering they are less of a madhouse company than Intel.
- himinlomax 6y agoI wonder how much of the delay in FPGA tech adoption is due to the utterly hilarious disaster that are the toolchains. They look like huge brittle proprietary monstrosities, incompatible with modern development methodologies.
- KSteffensen 6y agoAnd they are based on SystemVerilog and TCL, two of the worst programming languages in serious use. Those toolchain disasters are not quite as hilarious when you have to use them daily....
- himinlomax 6y agoTCL itself is not that bad for the purpose IMO; it's more the stuff around it, the proprietary binary formats, the gooey crap, and the non-open nature thereof.
- bsder 6y agoOy. I'm a Python guy, but Tcl is NOT that bad. Do not blame the horrible software engineering at Altera and Xilinx on Tcl. Those companies make more than enough money that they could sit down with Tcl and Tk, spend some time on the code, and have a quite decent tool. Instead, they keep their bitstream completely closed to lock out competitors and saddle the world with shitty tools. I'm really surprised that Lattice hasn't tried to go around Xilinx and Altera by doing exactly that. You would think that an open bitstream format and a couple million dollars thrown at academic researchers (Lattice makes about $200 million per quarter in gross profit) would produce some real progress, but I digress ... SystemVerilog, on the other hand, was specifically created because Verilog and SystemC got loose to the end users and the EDA companies were not going to make that mistake again. So, yeah, SystemVerilog is pretty bad.
- tails4e 6y agoOpen source tooling would not materalize if bitstream formats were opened, at least not competitive ones. Why? There are already open source versions for synthesis and PnR , and while functional they are very far off the 'terrible' EDA tools everyone rags on Xilinx for. The reality is SystemVerilog is a huge language, and already an open standard yet no open source project supports it fully, so I don't believe for a second if bitstreams were opened we'd see a load of top class tooling appear for synthesis and PnR. The reason is if it has not happened for the first (and arguably easiest) step in the chain i.e. System Verilog, they why would it happen for the others?
- dboreham 6y agoThis opinion is unlikely to be popular, and it's been decades since I was a full participant in the hardware business, but...I just have never seen the use case for FPGAs beyond niche prototyping / small run applications, which by definition make no money. I suppose there are also scenarios where you want to keep your design secret from the fab and/or change it every week, but those seem very niche too (NSA, GCHQ, ..?).
- moftz 6y agoEasily changing the design and being the cheaper option to ASICs for small productions are the two main uses for FPGAs. You may be designing a box that can be configured to do different things so you may want to support multiple FPGA images to switch back and forth depending on the mission. You may just want to be able to easily upgrade firmware for a complex design in the future. For Space DSP applications, the FPGA is king and will probably be for a long time simply due to the ability to cram a lot of functionality into a small space (DSP, microcontroller, combinational logic circuits, and massive I/O banks all in one chip)
- teleforce 6y agoI am not sure whether you are serious or trolling but I will bite ;-) FPGA are being used in many type of applications where real-time is necessary and non-recurrent engineering (NRE) cost need to be minimized, for example here [1]. One classic example is that if you poke under the hood of any signal generator like AWGs, you will probably find an FPGA inside. As you probably aware since you in hardware business, AWGs are probably one of most common equipment in any electronic and electrical labs or companies. [1]https://www.electronicdesign.com/technologies/fpgas/article/21776739/asiclike-fpga-methodology-saves-up-to-9925000-in-nre-costs https://www.electronicdesign.com/technologies/fpgas/article/...
- y2kenny 6y agoFor those who are not familiar, AWG stands for Arbitrary Waveform Generator.
- 6y ago
- ianhowson 6y agoIt's the usual "fundamental difficulty" with FPGAs -- CPUs and GPUs are faster and more power efficient for compute-intensive tasks. An algorithm on FPGA needs to overcome the 20x worse architectural efficiency just to break even with a CPU or GPU. The big benefit of having FPGA closely attached to CPU is that you can access the memory and internal buses quickly. Transferring stuff over PCIe hurts a lot. So you could make an argument for jobs using small work units requiring fast turnaround; CUDA kernels take milliseconds to launch. I worked with some of the early Xeon+FPGA parts and there just wasn't that much we could do with them. There wasn't enough fabric to build anything meaningful and we had an abundance of CPU cores, so the best we could do was specialized I/O accelerators.
- Symmetry 6y agoI think the more relevant comparison here would be ASICs. Softcores on FPGAs are indeed terrible but if you're implementing some algorithm directly at the gate level for cryptography or signal processing or whatever then being able to arrange inputs outputs into dataflows is a big win with no roundrips to general purpose registers or bypass networks. Not having to fetch instructions and being limited in paralellism is also a big win. And generally if you're doing something like mining bitcoin you should expect an FGPA to perform somewhere between an ASIC and a GPU. The problem is that if a task is common then someone is just going to make an ASIC to do it. And if its uncommon then the terrible FPGA software ecosystem and low prevalence of general purpose FPGAs in the wild mean that people will just do it on a CPU or GPU.
- ianhowson 6y ago> if you're implementing some algorithm directly at the gate level for cryptography or signal processing or whatever then being able to arrange inputs outputs into dataflows is a big win with no roundrips to general purpose registers or bypass networks This is true, but keep in mind that that sort of algorithm runs insanely well on any CPU or GPU because they, too, do not want to touch main memory. You would be blown away by how much work a CPU can do if you can keep the working set within L1 cache. Re. ASICs, it's a continuum: - "flexible, low performance, cheap in small quantities" (CPUs) - "reasonably flexible, better performance, cheap-ish in small quantities" (GPUs) - "inflexible, best performance, expensive in small quantities" (ASICs) FPGAs fit somewhere between GPUs and ASICs -- poor flexibility, maybe great performance, moderate small-quantity price. If your problem is too big for GPUs, as you say, sometimes it's easiest to jump straight to an ASIC. But it's such a narrow window in the HPC landscape. The vast majority of customers, even with large problems, are just buying a lot of GPUs. They're using off-the-shelf frameworks even though a custom CUDA kernel would give them 10x performance and 10% cost. The cost to go to an FPGA is too great and the performance gain simply isn't there.
- ip26 6y agoIt absolutely seems like there are some incredible opportunities in the high end. But as far as I know, FPGAs are quite area hungry which makes them inherently expensive. It's hard to think you'd find FPGAs of meaningful size included in $60 desktop CPUs, unless the harvesting opportunity is significant.
- MrXOR 6y agoBut FPGAs are the future. They will put the CPU out of work almost entirely. https://www.nextplatform.com/2020/01/31/when-will-fpgas-outweigh-cpu-in-compute-share/ https://www.nextplatform.com/2020/01/31/when-will-fpgas-outw... https://www.nextplatform.com/2018/03/19/fpga-maker-xilinx-says-the-future-of-computing-is-acap/ https://www.nextplatform.com/2018/03/19/fpga-maker-xilinx-sa...