Intel To Offer Custom Xeons With Embedded FPGAs For the Data Center
MojoKid (1002251) writes For years, we've heard rumors that Intel was building custom chips for Google or Facebook, but these deals have always been assumed to work with standard hardware. Intel might offer a different product SKU with non-standard core counts, or a specific TDP target, or a particular amount of cache — but at the end of the day, these were standard Xeon processors. Today, it looks like that's changing for the first time — Intel is going to start embedding custom FPGAs into its own CPU silicon. The new FPGA-equipped Xeons will occupy precisely the same socket and platform as the standard, non-FPGA Xeons. Nothing will change on the customer front (BIOS updates may be required), but the chips should be drop-in compatible. The company has not stated who provided its integrated FPGA design, but Altera is a safe bet. The two companies have worked together on multiple designs and Altera (which builds FPGAs) is using Intel for its manufacturing. This move should allow Intel to market highly specialized performance hardware to customers willing to pay for it. By using FPGAs to accelerate certain specific types of workloads, Intel Xeon customers can reap higher performance for critical functions without translating the majority of their code to OpenCL or bothering to update it for GPGPU.
Intel Xeon customers can reap higher performance for critical functions without translating the majority of their code to OpenCL or bothering to update it for GPGPU
In other words, to help prevent people from buying AMD and nVidia products.
"By using FPGAs to accelerate certain specific types of workloads, Intel Xeon customers can reap higher performance for critical functions without translating the majority of their code to OpenCL or bothering to update it for GPGPU"
LOL. But they will have to translate it to Verilog or VHDL, which is far harder.
*IF* its not some lame, slow, tiny array.. and if you get full access to it ( HDL or something )
---- Booth was a patriot ----
No ignore that entire last sentence, it's dumb. FPGAs don't do floating point very well for one and even their integer performance will never rival a GPGU either in performance, or power. For another, I can and do, use both FPGAs and OpenCL/GLSL in my daily life and would infinitely prefer to port my functions to OpenCL over an FPGA. It's quite a bit more work to synthesize and validate an FPGA design than it is to write OpenCL code and debug the usual way.
I think it's far more likely customers are implementing custom hardware solutions using the FPGA related to power management, server management and datastructure infrastructure that can only be done with an FPGA in certain power domains. I say this having designed servers and dealt with the feature requests.
By using FPGAs to accelerate certain specific types of workloads, Intel Xeon customers can reap higher performance for critical functions without translating the majority of their code to OpenCL or bothering to update it for GPGPU.
What? This doesn't make sense. Unless Intel invented a way to automatically generate parallel code (in which case it could also be used in GPUs), somebody would have to rewrite the relevant parts of the program in VHDL, Verilog, OpenCL, or whatever.
`echo $[0x853204FA81]|tr 0-9 ionbsdeaml`@gmail.com
As a hardware hacker, god I want one of these. On chip reprogramable DSP!? While it's a niche market, I'd love to get my hands on some, and not have to give up my favorite OS or build custom boards to do signal processing.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Dedicated FPGA HFT cards are ridiculously expensive. I wonder how integrated the FPGA will be in terms of interconnects with PCIE and the Xeon caches.
s/datastructure/datacenter/
caffeine, it's what should have been for breakfast.
High-Frequency Trading
FPGAs don't do floating point very well for one and even their integer performance will never rival a GPGU either in performance, or power.
Sure, and a hammer makes a terrible screwdriver. GPUs are specifically designed for register-to-register SIMD operations, so of course they are going to excel at that. But an FPGA is going to be better at bitstream operations, including many hashing and encryption algorithms.
Given that Intel added AES-NI without a ripple several years ago, and somewhat similar crypto acceleration functions were available on Geode LXes and some fairly antique VIA x86 cores(and very likely a lot of embedded stuff that was too feeble for much software crypto, albeit probably not exposed to anybody who hadn't sold their soul to qualcomm for BREW elite developer status or something), probably not many beyond whatever ones apply by default to all kinds of things.
As a matter of policy, the feds of the world appear to have largely recognized that the cat is out of the bag on strong crypto, algorithms and software move too easily, and doing it in software is too fast (for common purposes, obviously terminating a massive number of TLS connections or something isn't for the faint of heart).
They've not been shy about mandating 'lawful intercept' features, cultivating access to trusted links in the system, and ensuring that the overall level of security remains low; but the "Put your head in the sand and pretend that keys longer than 56 bits don't exist!" theory of regulation is largely a relic.
GPUs are primarily being used because everyone has one. FPGAs are about 10x faster and consume about the same amount of power as a GPU for stuff like bitcoin. the problem is the up-front cost and trust issues from the companies that make these pre-built FPGA boards.
> pretend that keys longer than 56 bits don't exist!" theory of regulation is largely a relic.
But the law still sets a limit at 64 bits and requires you to get an export license for anything beyond.
I should use this sig to advertise my book ISBN-13 : 978-1501515132.
Dude, Altera FPGAs already do OpenCL (says me, a guy who helped implement it).
I have a friend in that in graduate school used a motherboard that could take an Altera FPGA in one of the Xeon sockets. This seems like the next logical step; hopefully it's not too expensive so that the hardware is accessible to hobbiest/engineers. I am happy that both Xilinx and Altera offer cheap development boards so that we can play with the new offerings. It's easier to convince a boss to use it if we're familiar with it. (hint hint, wry grin)
I use the zynq processor at my job, and am very happy with the amount of flexibility you can get out of an embedded system having access to the FPGA and processor fabric; you can directly access gigasample ADC's, etc. When I first got into embedded systems on an FPGA, the processor was a soft-IP and not terribly fast. Both Xilinx and Altera now offer ARM processors that run up to 1GHZ. The amount of system flexibility is great. You can make major architectural choices without changing the hardware. You might have a data-path, or computation that is simply too intensive for a processor to handle.. You have the flexibility to port this portion to the logic side. If you're in a rapid prototyping mode and are constrained by board size and mechanical packaging constraints, FPGAs are great.
Debugging SoC still has it's challenges though. It's easy to program FPGAs, and easy to program the microprocessor. The tools are still a little clunky from Xilinx or Altera to handle their hybrid SoC parts. There is still work to be done to make them work more seamlessly.
Think of the fun that could be had with this. Fits in the same socket and does who knows what.
Of course, bitcoin mining using the SHA256 hash which is not a typical application for a GPU. It involves a lot of shuffling at the bit level, which a GPU was not designed for. For some other workloads, involving standard math operations, or large amounts of memory bandwith, the GPU will likely be faste.r
True, though you'll note that many of the changes in the linked document refer to loosening after encryption systems were removed from 'munitions' classification and assorted expansions of 'self-report', new categories with reduced reporting requirements, and so on.
I have no doubt that the amount of paperwork require to fully comply with the law in exporting something every war3z kiddie in Iran already has is still silly, and I don't doubt that there's a cube somewhere in Intel Inc. whose salary is justified by filling it out; but this isn't the big flap over PGP era. I'm not sure that the regulations will ever die off entirely, especially the stuff governing large outfits, since the marginal cost of one extra form is so low; but as a matter of strategy direct attacks on cryptographic systems have substantially faded (since you can't keep software away from criminals, and you can't bank safely with stuff law enforcement can easily brute force) in favor of RIPA/CALEA style legislative compromises.
what about the ram / pci-e lanes that are part of the socket?
Maybe in 4 way boards or some 2 socket boards.
2 socket broads can work with only 1 cpu. But what will they do when they see a filled socket but no ram and no PCI-E io?
This explains why Intel was selling fab time to an FPGA vendor.
How can they be used for interconnects?
The CPU fits in the same socket an existing Xeons.
Looks more like a way to compete with AMD+GPU with just an Intel CPU.
I don't know what you're talking about here
They're not selling FPGA's in an Intel socket. They're selling Xeon CPU's with integrated FPGA's.
Image a Beowulf cluster of these!
Competition Good, Monopoly Bad.
That's great, so they're going to port their code to Open CL, then run it on your FPGA? Why not just buy a GPU and plug it in?
If they're really set on your FPGA, why not buy a PCIe attached version of your FPGA? Xilinx has them and they go up to pcie v3 x8? What about power? Datacenters care, FPGAs are going to use more power. Why is this a good idea?
Intel has already come up with an Atom CPU with integrated FPGA, but only for the embedded market.
I'd already been thinking about the possibility of end-user-accessible, on-the-fly-reprogrammable FPGA functionality as part of a "regular" computer before I heard Intel had produced an integrated CPU/FPGA (though it's not clear how easily configurable the FPGA was there). I raised the issue in that previous thread and got a *very* interesting and informative response (thank you Tacvek) that pointed out some major problems with the concept of general access to such functionality.
The issues raised there explain why Intel are unlikely to be making an easily-reconfigurable hybrid product like this available to the general public any time soon, however smart and exciting the idea sounds.
"Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
'Cryptocoin mining'.
Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
So, does the FGPA "code" get swapped on a context switch?
Watch this Heartland Institute video
Some workloads perform much better on an FPGA, notably, realtime encoding/compression of HD H.264 video. I know because I've worked on such a broadcast quality encoder [currently being used by some major distribution outlets]. While you're right that it's harder to program an FPGA [in particular, validate the design], the performance gains can be huge. In particular, calculating motion vectors gets a win.
Note that H.264 DCT's are integer ones. And, with Intel's hybrid/onchip implementation, the FPGA logic could have access to the CPU's SIMD FP hardware. With Intel's hafnium and trigate technologies, adding the FPGA won't consume that much additional power.
Also note the benefits for search in an article just published today: http://arstechnica.com/informa...
Like a good neighbor, fsck is there
I bet HF trading ends up being a prime market for this technology.
In the course of every project, it will become necessary to shoot the scientists and begin production.
I hope they allow customer instructions like the NIOS soft CPU in Altera FPGAs. This lets you create customer HW to implement some function at the ISA level... Altera lets you do single or multi cycle return. And auto generates either an instruction for ASM use or some stubs for C. It really is super useful.
"Bob, we're glad you Intel boys have finally come around".
"Hi Jeff. Yeah, well we just about got the marketing boys convinced enough to run with it. They managed to find an angle that flies pretty well. Gets us off the hook and gets your boys into a heck of a lot of servers!"
"Hey, it's a win-win so far as I'm concerned. Wish it could have been sooner though, but what with all this pressure from the purse-holders, we couldn't bankroll it for you".
"Times are getting tough, huh? It wasn't that long ago you NSA boys had infinitely deep pockets".
"The times we live in, Bob. What can you do?".
"You need any help with the rootkit code? Some of our wizards are pretty good"
"Thanks, Bob, but we already have it covered".