8 ms·
So, about 15 years ago I took a college course on microprocessor design, and our final project was to implement a simple microprocessor on an FPGA. At the time
by crazygringo 13y ago
So, about 15 years ago I took a college course on microprocessor design, and our final project was to implement a simple microprocessor on an FPGA.
At the time, it seemed obvious that, over the next decade, FPGA's would work their way into general-purpose computing, so that (for example) Photoshop filters would simply reconfigure the FPGA to run blazingly fast. Likewise with games, or video codecs, or 3D rendering, or whatever else was processor-intensive.
But that clearly hasn't happened. Instead, GPU's took off as the main computational supplement to CPU's.
Does anyone here have any insight as to why? Is there a technological reason why FPGA's never turned into general-purpose hardware standard on every desktop and laptop? Has it been a chicken-and-egg problem? A standardization problem? Or something else? Do FPGA's still have potential for general-purpose consumer computing? Or are they going to be forever relegated to special-purpose roles?
- lucian1900 13y agoGPUs were "there" and there was a logical path towards increasing their usefulness. It was partly an accident that they're not more programmable. Technology sucks :(
- al2o3cr 13y agoOne guess would be that GPUs address a wider market segment (everybody needs a display + hardware to drive it). More people buying GPUs, lower prices, more $$$ for R&D, repeat. Another likely issue with FPGAs is that for everything but raw compute they still need support circuitry (physical I/O ports, memory interfaces, etc) that are different for every app but not really "reconfigurable" in the same sense as the FPGA fabric. Finally, I'd wonder if reconfiguration time is part of the problem - until relatively recently, reconfiguring an FPGA was all-or-nothing and could take multiple milliseconds. Not a big deal when configuring a device once on boot, but serious headwind when trying to context-switch between different jobs that need FPGA assistance.
- pdq 13y agoMoore's law is quite amazing. I believe there are 4 reasons why GPUs have taken off conventionally as compared to FPGAs: 1. Last I checked, the FPGA vendors will not open their toolchains up, and not even document the bitstream formats. They will claim NDA, proprietary, etc. This has the massive side effect that you are stuck with their bloated, slow, crappy toolchains. If this were open, I guarantee hackers would be inventing all kinds of interesting ways to convert their software into FPGA bits. 2. FPGAs are VERY hard to write and debug. You have to write your design in an HDL language (either VHDL or Verilog), and you have to use a software simulator to prototype the design on first (and of course these tools are either quite pricy or if free they are usually limited or hard to use). Then you can synthesize the design and download it into the FPGA for running. The next problem is debugging your design. The entire internal state of the FPGA is only accessible through slow scan, unless you dedicate a portion of your design to "monitors", which tap the traffic and store their values into internal RAMs. So you may have to respin the design just to get more monitors to debug where the issue is. 3. FPGA compilation is SLOW. When I used them professionally a few years ago, a Virtex5 could take multiple hours to resynthesize/place & route a medium-sized design. I believe that Virtex7 they are advertising could take over a day to respin if you change your design. 4. Most new machines already have a built-in graphics with a GPU that can be utilized as a general-purpose GPU. No one ships FPGAs in any conventional computer.
- JamilD 13y ago(2) can probably be addressed with OpenCL -- Altera seems to be working an SDK[1] that allows you to write C code which, as I understand it, would compile to an image that you could then program on to your FPGA (or you could just compile for execution on a processor). So fortunately, no Verilog or VDHL necessary. (3) is another issue, but I don't think the consumer would necessarily need to worry about compilation. The developer would just include the compiled programming files for different FPGAs in the application. If you mean that it'll be slow on the developer's side, that's definitely a valid point. I'm sure, however, that you'll see FPGA manufacturers start to move toward remote compilations so that you're not necessarily limited by the hardware you have in-house. [1] http://www.altera.com/products/software/opencl/opencl-index.html#sdk http://www.altera.com/products/software/opencl/opencl-index....
- sounds 13y agoMore about (3): Altera calls it "logiclock," Xilinx has a different term, but the idea is that you don't need to re-synthesize the entire FPGA for every change. In fact, you may not want to. If you are tweaking a certain region, you're usually happier if the place & route doesn't send your stuff through a route that then kicks off a line in another block so that the timings are now off in that other block. For an FPGA the timing is how you measure performance and getting the best timings can take quite a bit of work. Being able to lock that once you've got it right is a big plus.
- prutschman 13y agoXilinx's ISE calls it "SmartGuide". It's kind of a mixed bag. It's worked okay for me if changes are truly minor, but if there are large changes to the logic it doesn't seem to be very good about "forgetting" what it learned from the previous pass. Three or four times this week I've had a design fail to make timing with SmartGuide, but work when doing P&R from scratch.
- hugway 13y agoRegarding (3) remote compilations, Altera is lifting off the hardware burdens for developers with remote compilations on cloud. see cloud.altera.com for Altera's tool extension
- kryptiskt 13y agoAnytime an algorithm is important enough to be of interest for hundreds of millions of user it is worth the investment to etch its primitives into silicon. And if there are new and exciting computations that will only be in hardware next year, CPUs are powerful enough that software can tide us over until the silicon arrives.
- anigbrowl 13y agoEspecially when the price of entry to ASIC land is relatively low by industrial standards - http://electronics.stackexchange.com/questions/7042/how-much-does-it-cost-to-have-a-custom-asic-made http://electronics.stackexchange.com/questions/7042/how-much... eg for something very simple you can do it for thousands or tens of thousands...but in that price range it's probably still more economical to implement in software or do it discretely with SMT unless you are very sure about the existence of a market.
- hershel 13y agoIt's not cheap. If you want to compete wit cpu/fpga/gpu ,you'll need to use the latest manufacturing processes and do complex designs,and now we're talking about more than 100 million USD investment.
- pjc50 13y agoNot unless you're trying to compete with Intel. Consider the various bitcoin ASIC miners: beat all other technologies for solving that problem for an investment of a few million. However, algorithms are so rarely the stumbling block for applications; data storage, management and communications are. The major exception is graphics, hence the GPU.
- hershel 13y agoa bitcoin miner isn't a isn't a general processing unit.It does something specific that's very very easy to optimize and implement, and you don't use latest manufacturing process but tools like easic , hence the small investment.
- jbp 13y agoI also had to implement simple microprocessor on an FPGA about 10 years ago. I think one of the main reason is programming the FPGA is not easy, the tools needed for FPGA development are all proprietary. Every FPGA has different way to program it.
- anigbrowl 13y agoI think GPUs took off because the specific problems they solve were quite well-defined and enough people in the videogame/3d grapics market agreed about which protocols to use. Even for things like Photoshop and other general-purpose graphics software, GPU support seems to be a bit hit and miss. I actualy have 2 FPGA-based devices that I use daily - polyphonic analog synthesizers, to be specific. Manufacturers are tight-lipped about how they're using the FPGAs, but it appears to be for ultra-rapid reconfiguration of analog circuit topologies without the load time delays that result from a traditional microcontroller > D/A converter arrangement. There are also field-programmable analog arrays on the market, but I have yet to see one in a commercial product and it seems like they have some way to go before being economical for audio synthesis applications. I love FPGAs although I don't know much about how to et started with programming them. There is an ASIC coming out of patent in a year or so which I'd like to re-implement in an FPGA package, and I've thought about reaching out to the original architect who lives nearby and is a friendly fellow. I'm not sure how feasible this is, though.
- rjsw 13y agoTo get started with FPGAs just download one of the free IDEs and have a play. You can buy dev boards for under $100 to get some feedback that what you are doing really works.
- adamnemecek 13y agoCan you recommend some boards? Whenever I looked into it, I got overwhelmed with all the options and I was not quite sure what to look for.
- thrownaway2424 13y agoMost applications don't really need the flexibility of an FPGA. Just having massively parallel multiply-accumulate turns out to cover huge amounts of digital signal processing and machine learning applications. A long time ago computers sometimes came with DSPs dedicated to Photoshop-like programs. The GPU is a logical extension of that. The FPGA is something entirely different.
- hershel 13y agoIn general GPU's are same or better in floating points per given area of silicon. on top of that , FPGA's add other expenses due to lower market size. Maybe FPGA's are competitive in integer math, but that's a pretty small niche ,not big enough for a coprocessor.
- pkaye 13y agoFPGA are still more costly when compared to ASIC in large volume. Some of these high end FPGA can run $1K to $10K assuming you have even access to them due to their limited availability.
- 8_hours_ago 13y agoSomewhat tangential, but the open hardware laptop that bunny and xobs are designing has a built-in FPGA, so you aren't the only person who thinks it would be nifty to have one. Personally, I think it'd be lots of fun to hack with and would open up a lot of interesting projects (perhaps a port of the 2048 game to an FPGA??). http://www.kosagi.com/w/index.php?title=Novena_Main_Page http://www.kosagi.com/w/index.php?title=Novena_Main_Page
- revelation 13y agoThey don't have that FPGA to offload the CPU, I think its rather to interface with external components. GPUs don't come with external IO and for a lot of high-speed buses you are just dead in the water without an FPGA to handle the delicate timing. That is really the unique benefit of FPGAs: the implicit parallelism makes them a really great fit for the kind of high-speed bit banging that would be impossible to get right on a normal CPU (not to mention very difficult to program in the first place).
- agumonkey 13y agoI wonder how many people would have bet on GPUs in the late 90s. Even high-end 3d chipset were ousted quite brutally (3dlabs, evans & sutherlands) from the gpu market by small 'gaming' companies. And now they invade server side computations... quite funny.
- sliverstorm 13y ago1) FPGAs are not easy to develop for, and totally different from the skillset of a Photoshop developer. It is not as easy as dreaming up a design and pressing a button; if you are anywhere close to pushing the envelope it takes expertise & time. 2) GPUs, being purpose-built and mass-marketed, are both much cheaper and much faster. Think of the Ford Fiesta ST vs. a Jeep Wrangler. The Jeep is simple & more reconfigurable, yet is slower and more expensive- for exactly those reasons! 3) GPUs and CPUs compliment eachother well. The only gap is heavily parallel branching code- GPUs are bad at if-statements, CPUs are bad at heavily parallel. But a branch predictor is the key to if-statements, and branch predictors are hard. FPGAs are fundamentally a prototyping tool. Can you think of examples of prototyping tools that eventually broke into the main market, replacing the incumbent product?
- aortega 13y ago>FPGAs are fundamentally a prototyping tool. Can you think of examples of prototyping tools that eventually broke into the main market, replacing the incumbent product? Python
- adwn 13y ago> FPGAs are fundamentally a prototyping tool. FPGAs can be used for prototyping ASICs, but that's by far not their major use-case.
- sliverstorm 13y agoWhat is then? I know they are used alongside PLDs, but I thought PLDs still dominated that use-case.
- adwn 13y agoThey are essentially low-volume ASIC replacements. Some applications: - digital signal processing (DSP) - network equipment (modern high-end FPGAs are able to function as 100G Ethernet switches and routers, just connect them to some PHYs and fast DRAM) - systems on chip (SoC): processor, fast DSP, all kinds of IOs, memory controller – all on a single chip - realtime video stream processing For more examples, see http://www.xilinx.com/applications/index.htm http://www.xilinx.com/applications/index.htm
- aortega 13y agoVery few common user tasks can be solved more efficiently with an FPGA than with a CPU or GPU. CPU gives you speed in computation. Except for a custom ASIC, nothing can match a modern CPU in single thread speed. GPUs gives you parallelism. You can get thousands of decent CPUs in cheap boards today. IMHO FPGAs main advantages today are bandwidth and auditability. But neither are very important in most applications.
- NickNameNick 13y agoDidn't Cyrix cpus have some fpga in them, that would be dynamically assigned to any repetitive code that the cpu was busy doing?
- femto 13y agoA contributing factor is that the Partition-Place-Route (PPR) software, that is necessary to map a design onto the FPGA die, is proprietary and controlled very tightly by the FPGA vendors, as are the specifications of the raw dies and the meaning of each bit in the corresponding bitstream. Consequently, FPGAs don't lend themselves to an uncontrolled explosion of innovation. Compare with GPUs and CPUs where open source compilers are available and anyone can have a crack at innovating, at whatever level they choose. As an example, if you want to dynamically generate programming for a Xilinx FPGA, you need to incorporate Xilinx's binary only PPR program somewhere into the flow. That acts as a ball and chain around the leg of reconfigurable computing, impeding its development and adoption.
- adamnemecek 13y agoMacbooks supposedly contain FPGA chips (Google around but it's mentioned for example here [1] go to "step 13"). I was trying to look into it a while back but I don't think I ever got some definite answers as to what they are used for. [1] http://www.ifixit.com/Teardown/MacBook+Pro+15-Inch+Unibody+Mid+2012+Teardown/9515 http://www.ifixit.com/Teardown/MacBook+Pro+15-Inch+Unibody+M...
- wtallis 13y agoFPGAs aren't particularly hard to find in the PC ecosystem, especially on first-gen parts or custom jobs like Apple machines. I've seen some SSD and RAID controllers ship as FPGAs, and some sound cards bundling them for DSP use. They're usually not reprogrammable.
- deleted 13y ago[deleted]
- InclinedPlane 13y agoSpeed. Reconfiguring an FPGA is a very slow process, and FPGA's can't match the clock speeds of conventional ASICs. That may change in the near future with FPGA-like devices built using memristors, which potentially could be reconfigurable at the speed of writing RAM and run at the same clock speeds as any ASIC.
- p1esk 13y agoActually, modern FPGA are "capable of dynamically reconfiguring at multi-GHz rates": https://www.tabula.com/technology/technology.php https://www.tabula.com/technology/technology.php
- InclinedPlane 13y agoThat's marketing hype. If you reconfigure just one gate it can be extremely fast, but typical FPGAs take a significant fraction of a whole second to reconfigure. Though they are getting faster over time.
- p1esk 13y agoDid you even read how their chips work?
- dmytrish 13y agoI have very limited knowledge of the subject, but I had an impression that GPUs started to catch up on programmable capabilities with shaders. As far as I know, shaders reprogram the rendering pipeline, so is it a kind of specialized HW programming?
- ANTSANTS 13y agoHow do you virtualize an FPGA? A GPU can be virtualized and shared between several processes. It takes waaay too long to flash an FPGA to implement time-division multiplexing on it. All you can do is "slice up" the FPGA and give different processes different portions, and even that is a security vulnerability waiting to happen unless the FPGA is designed to keep these "blocks" separately contained. How do you balance the need for high-performance communication between the FPGA and the rest of the computer with the inherent inability to trust whatever configuration has been loaded into the FPGA? Software security is hard enough without infinitely reconfigurable devices lurking inside our machines. How does a possible FPGA configuration work optimally across a wide variety of FPGAs (which can have various "built-in", non-reconfigurable components) and sizes that can only be determined at "flashtime"? What exactly do regular users need an FPGA for that isn't already handled by dedicated silicon with much greater performance and much less power usage than an FPGA would? EDIT: I'd like an FPGA card for my PC just for running FPGA "emulators," because you can recreate a SNES or whatever in a tiny fraction of the gates that you need to make a CPU capable of emulating it with cycle accuracy at full speed. I seriously doubt there's much demand for that, though: if you're going to go to the trouble of buying special hardware for emulation, you might as well just buy the console and a flash cart.
- crazygringo 13y agoI would imagine that the FPGA would not be shared. Much like only one app can be full-screen on your computer, only one process could use the FPGA. The OS wouldn't let a second process use it if a first process already was. As for regular users, personally I'd like it for video codecs. I'd like it for video transcoding. I'd like it for faster MP3 encoding. I'd like it for Photoshop filters. I'd like it for speech recognition. I'm sure I could think of things that other users would like to use it for, like 3D rendering. I don't know of dedicated silicon that does ANY of these things, except specifically for H.264 decoding. That's it. And the thing is, for all the items I've listed, it's totally fine that my computer is only ever doing one of them at a time. These are all "regular user" uses, whereas virtualization is not needed very much for regular users.
- mprovost 13y ago
- Brashman 13y agoI think a big reason is the chicken-and-egg problem. GPUs gained large spread adoption because of their use for gaming. It's only relatively recently that they've been exploited for more general compute purposes. There hasn't really been a "killer app" for FPGAs that warrants many people to have one.
- listic 13y agoMaybe in the next 5 years, when Moore's law may run out http://en.wikipedia.org/wiki/5_nanometer http://en.wikipedia.org/wiki/5_nanometer (unless Intel et al. have some extraourdinary technology up their sleeves) we will finally see the advent of FPGA's? Without the annual growth of transistor density, the second best avenue to gain performance will probably be specialization, and reconfigurable specialized hardware looks more attractive than fixed one.
- goalieca 13y agoGiven everyone would have different models, the compilation process (including placing and routing) would absolutely destroy things. I've seen them take 1+ hours on a fairly fast machine. The problem with connecting N logic blocks is that you need N^2 buses to connect them directly to one another. Luckily they aren't but that's why the placing/routing optimization problem takes so long to compute as transistor count is now in the billions.
- TD-Linux 13y agoI can answer this, as an electrical engineer. FPGA's are horrendously inefficient, space and power-wise, for many tasks. Much of the core is taken up by the programmable routing between different components, and generally most components will be not fully utilized (such as LUTs and RAM). Yes, the Virtex-7 (a VERY EXPENSIVE fpga) can hold 1000 very simple 32 bit cores.... but a top end NVIDIA GPU has 2688 CUDA cores. While not entirely independent, these CUDA cores have far deeper pipelines and far superior ALU's to the one in the article. If your software fits the programming model, GPUs will handily beat a FPGA. FPGA's are great for prototyping ASICs, and cases where timing is of critical importance - try implementing a VGA video generator on a CPU. Basically everywhere an FPGA would excel, an ASIC excels more, but FPGAs are great for low volume and or specialty hardware where a GPU is not good at accelerating the task at hand.
- hrjet 13y ago> the Virtex-7 (a VERY EXPENSIVE fpga) can hold 1000 very simple 32 bit cores.... but a top end NVIDIA GPU has 2688 CUDA cores. But the point of the FPGA is to not build cores inside it; the OP article is just an exercise. Application specific logic built with FPGA might be much more efficient than generic CUDA cores. Also, it is a given that an ASIC will be more power efficient than an FPGA, but the FPGA will be generic and hence more money efficient.
- damian2000 13y agoAgree with yout points that FPGAs are great for low volume prototyping/one-offs, interfacing, and when timing is of critical importance.
- frozenport 13y agoThey were used in the late 90s, and companies such as Cray had C to FPGA compilers. These were implemented as c style calls that the compiler transformed to FPGA. The coding was hard and performed below expectation. The only customers that benefited were military/intelligence agencies who were using outdated techniques such as filtering in the Fourier basis. The problem was data-transfer compounded by inflexible code generation. The data still needed to travel from RAM which meant that even without computation you couldn't get over a 50% increase in performance. It would need to be send back for more complex processing.
- hyp0 13y agoNot a direct answer, but it's not just GPUs: on ARM "System on a Chip", you can get all sorts of components: audio, hardware codecs, networking, radio, and low-power companion cores (littlebig). So, your vision of general-computation-in-silicon has occurred, just static, not dynamic.
- _pmf_ 13y ago> Does anyone here have any insight as to why? 1. They are already there in commodity HW. 2. GPU vendors make money with their hardware; they need not extort developers for a development environment like FPGA vendors think they have to do. Therefore, development for GPUs has a lower barrier of entry.