6 ms·
Flow Computing aims to boost CPUs with ‘parallel processing units’
- brotchie 2y ago“Now, the team is working on a compiler for their PPU” good luck!
- greenavocado 2y agoIs this like the Itanium architecture with its compiler challenges?
- claxo 2y agoIndeed, a very smart compiler would be necessary, perhaps too much for the current compiler art, like the itaniun. But...how about specializing to problems with inherent paralelism? LLMs maybe?
- Kon-Peki 2y agoThe Itanium C and FORTRAN compilers eventually became very, very good. By then, the hardware was falling behind. Intel couldn't justify putting it on their latest process node or giving it the IPC advancements that were developed for x86. If you wanted to do something similar right now, it's possible to succeed. Your approach has to be very different. Get a lot of advancements into LLVM ahead of time, perhaps. Change the default ideas around teaching programming ("use structured concurrency except where it is a bad idea" vs "use traditional programming except where structured concurrency makes sense", etc) But no, throwing a new hardware paradigm out into the world with nothing but a bunch of hype is not going to work. That could only work in the software world.
- bhouston 2y agoWhile the Itanium failed the Ageia PPU did succeed with its compiler. It was acquired by NVIDIA and became CUDA. https://en.wikipedia.org/wiki/Ageia https://en.wikipedia.org/wiki/Ageia
- gdiamos 2y agoIt did indeed get merged into the CUDA group but I think the internal CUDA project predated it, or at least, several of the engineers working on it did
- mepian 2y agoThat's not the same PPU, is it?
- gregw2 2y agoI always thought CUDA grew out of Ian Buck's PhD thesis under Pat Hanrahan; why do you credit Ageia?
- yeahwhatever10 2y agoWhen will we get the “Mill” cpu?
- mshook 2y agoAt this point, probably never it seems...
- rbanffy 2y agoAnd considering their effort in patenting every idea related to it, we’ll only see it when the first implementer gets sued.
- theLiminator 2y agoI've been following that saga for a long time. Seems mostly like vapourware sadly.
- XorNot 2y agoProbably implementation hell. The big idea theoretically works, but when you get into the details the compromises for implementation steal away the gains. I'm always reminded of the rotary internal combustion engine: in theory there's a whole suite of benefits, in practice they're "interesting" but not that great once practically built.
- sparkie 2y agoMore time spent filing patents than implementation.
- interroboink 2y agoSeems like a nice idea — instead of the stark CPU/GPU divide we have today, this would fit somewhere in the middle. Reminds me slightly of the Cell processor, with its dedicated SPUs for fast processing, orchestrated by a traditional CPU. But we all saw how successful that was (: And that had some pretty big backing. Overcoming the inertia of the current computing hardware landscape is such a huge task. Maybe they can find some niche(s).
- winwang 2y agoI'd believe more in a heterogenous chip (e.g. MI300X, Apple M series, or even APUs) than in completely new chip tech.
- rbanffy 2y agoIt’s still two separate ISAs.
- winwang 2y agoI have a hard time believing that dealing with a singular ISA for two different compute cases would be an "obviously better" solution. I don't doubt that it's plausible/possible, especially if RISC-V + extensions are still simple, but then again, that's far outside my wheelhouse.
- rbanffy 2y agoEven with a GPU sharing memory with your CPU, calling GPU code is never as simple as doing a jump to that code. You need to set up the code the GPU will run and then let it loose on the data.
- mnky9800n 2y agoAlso thinking machines corporation https://en.wikipedia.org/wiki/Thinking_Machines_Corporation https://en.wikipedia.org/wiki/Thinking_Machines_Corporation
- 2y ago
- gnabgib 2y agoDiscussion (28 points, 3 months ago, 32 comments) https://news.ycombinator.com/item?id=40650662 https://news.ycombinator.com/item?id=40650662
- johnklos 2y agoTell us something new, please.
- johnklos 2y agoThis is a duplicate of https://news.ycombinator.com/item?id=40650662 https://news.ycombinator.com/item?id=40650662, and this article has nothing new in it.
- Animats 2y agoDoes anyone know what they mean by "wave synchronization"? That's supposedly their trick to prevent all those parallel CPUs from blocking waiting for data. Found a reference to something called that for transputers, from 1994.[1] May be something else. Historically, this has been a dead end. Most problems are hard to cut up into pieces for such machines. But now that there's much interest in neural nets, there's more potential for highly parallel computers. Neural net operations are very regular. The inner loop for backpropagation is about a page of code. This is a niche, but it seems to be a trillion dollar niche. Neural net operations are so regular they belong on purpose-built hardware. Something even more specialized than a GPU. We're starting to see "AI chips" in that space. It's not clear that something highly parallel and more general purpose than a GPU has a market niche. What problem is it good for? [1] https://www.sciencedirect.com/science/article/abs/pii/0141933194900051 https://www.sciencedirect.com/science/article/abs/pii/014193...
- bhouston 2y agoGPUs have wavefronts so I assume it is similar? Here is a page that explains it: https://gpuopen.com/learn/occupancy-explained/ https://gpuopen.com/learn/occupancy-explained/
- adrian_b 2y agoNope. AMD's "wavefront" is an obfuscated word for what NVIDIA calls "warp". NVIDIA's "warp" is an obfuscated word for what has been called for many decades in the computer literature as "thread". (NVIDIA's "thread" is an obfuscated word that means something else than what it means in the non-NVIDIA literature.) NVIDIA has thought that it is a good idea to create their own terminology where many traditional terms have been renamed without any reason. AMD has thought that it is a good idea to take the entire NVIDIA terminology and replace again all terms with other words.
- mystified5016 2y agoI'd assume that 'warp' is taken from textiles: https://en.m.wikipedia.org/wiki/Warp_and_weft https://en.m.wikipedia.org/wiki/Warp_and_weft A warp is a thread, but a thread within a matrix of other threads. I'm not into GPU programming, but doesn't nvidia have some notion of arranging threads in a matrix sort of like this?
- petermcneeley 2y ago> Now, the team is working on a compiler for their PPU I think a language is also required here. Extracting parallelism from C++ is non trivial.
- poincaredisk 2y agoSomething similar to CUDA or OpenCl should do it, right?
- throwawayffffas 2y agoHow is this different from an integrated gpu other than it presumably doesn't do graphics.
- pier25 2y agoI'm probably missing something but why not use gpus for parallel processing?
- JackSlateur 2y agoBecause GPU are physically built to manage parallel task, but only a few kinds They are very specialized CPU are generics, they have lots of transistors to handle a lot of different instructions
- Groxx 2y agoAlso moving data to and from the GPU takes MUCH more time than between CPU cores (though combined chips drastically lower this difference).
- markhahn 2y agoin the olden days of gp-cpu this was certainly true. is it still true? do you just mean "latency overhead for setting up a single PCIe transaction is much larger than flinging a cache line across QPI/etc"?
- markhahn 2y agoI think this is a really unfortunate way to explain it. The issue is not that CPUs have a lot of different instructions - hardly anyone uses decimal math instructions, for instance, and no one cares about baroque complex addressing modes. The difference is that GPU code is designed to tolerate latency by having lots of loop iterations treated as threads. A modern CPU tolerates latency by maintaining the readiness of hundreds of individual instructions ("in flight") - essentially focusing on minimizing the execution latency of each instruction. (which also explains how CPUs use caches and very high clocks, but wind up with somewhat fewer cores and threads.) (note that I'm using cores and threads correctly here, not the nvidia way.)
- nine_k 2y agoGPUs work on massive amounts of data in parallel, but they execute basically the same operations every step, maybe skipping or slightly varying some steps depending on the data seen by a particular processing unit. But processing units cannot execute independent streams of instructions. GPUs of course have several parts that can work in parallel, but they are few, and every part consists of large amounts that execute the same instruction stream simultaneously over a large chunk of data.
- elromulous 2y agoDoes anyone have any knowledge/understanding on how this is (or isn't?) fundamentally different from Intel's Xeon Phi? https://en.wikipedia.org/wiki/Xeon_Phi https://en.wikipedia.org/wiki/Xeon_Phi
- CyberDildonics 2y agoHow is it the same? The Xeon Phi was basically just smaller/weaker cores but more of them and with their SIMD units still there.
- exabrial 2y agoI’m still waiting for a clockless core… some day
- aidenn0 2y agowww.greenarraychips.com
- jecel 2y agoIf I understood correctly, the GreenArray chips don't have a clock but each individual core does via a local ring oscillator. So it might run at a different speed than its neighbors and the communication system handles that. A more famous clockless processor was Amulet, an asynchronous implementation of the ARM. https://en.wikipedia.org/wiki/AMULET_(processor) https://en.wikipedia.org/wiki/AMULET_(processor)
- aidenn0 2y agoI can't prove you wrong, but the documentation for the F18A core seems to imply it's asynchronous: > The F18A is built from asynchronous logic, therefore its instruction times are naturally approximate. The time required for all activity varies directly with temperature, inversely with power supply voltage (VDD), and randomly within a statistical distribution due to variations in the process of fabricating the chips themselves. Additional variations may occur with minor revisions in the version of F18 technology used by a particular chip. Applications should not be designed to depend upon the speed of activities within F18 computers for timing purposes without taking all of these variables into consideration. https://www.greenarraychips.com/home/documents/greg/DB001-221113-F18A.pdf https://www.greenarraychips.com/home/documents/greg/DB001-22...
- jecel 2y agoI am more familiar with the F18A predecessors, such as the F21, than with this design. So it is quite possible that it is a proper asynchronous processor even if the older ones were not. I am biased by some confusion I observed about the F21. There are two ways to design an ALU: an efficient solution is to combine the inputs and control signals using as little logic as possible to generate the results or to have a separate circuit for each operation and then have the control signals use a multiplexer to select the desired result. A great example of the first style is the ALU in the ARM1: http://daveshacks.blogspot.com/2015/12/inside-alu-of-armv1-first-arm.html http://daveshacks.blogspot.com/2015/12/inside-alu-of-armv1-f... Many simple educational processors use the second style, as did the F21. In addition, the adder in the F21 was a simple ripple carry adder. In theory, you would have to use a clock slow enough that the + instruction would have enough time to generate the correct result even in the worst case. In the first ALU style that would certainly be true, but with how the F21 was actually designed just executing one or two NOP instructions before the + would work just as well. As soon as the values of the T and N registers were stable the adder would start to ripple and calculate no matter what instructions were being executed. Only when we get to the end of the + instruction does the result need to be ready. This allowed the amazing demonstrations of some F21 chips, which used 800nm technology, running at 800MHz. This hand scheduling of code to allow frequencies beyond what some instructions could handled was described at the time by several people as being an asynchronous processor design, which is wasn't. That is why I am a bit wary when I see that term used for the descendants of the F21 even if it turns out to be correct. Another interesting issue with running the F21 at 800MHz was that Chuck Moore's OKAD tools did not originally simulate heat transfer. As a result two transistors were a little smaller than they should have been and could burn out at such high frequencies. Inserting NOPs between instructions allowed these transistors to cool down enough not to be a problem. His next version of OKAD included a neat thermal model in order to avoid that mistake in future designs.
- somat 2y agoWhenever I see the word "fintech" this is the article I am expecting, Instead I am disappointment with some drivel about banks. I am not sure what is wrong with me, you would think my brain would have figured it out by now, but it always parses it wrong. perhaps if it were "finctech" that would help.
- cryptoz 2y agoI’ve not yet had this problem but I surely will now! Thanks I guess.
- imtringued 2y agoThe word "fintech" is disappointing, most because everyone calls their classical old school finance company a fintech that has a minor tech component. E.g. something like Solaris Bank is a fintech, but BaaS providers are a rarity and not the average fintech.
- wmf 2y agoThis is based on legitimate (although second-tier) academic research that appears to combine aspects of GPU-style SIMD/SIMT with Tera-style massive multithreading. (main paper appears to be https://www.utupub.fi/bitstream/handle/10024/164790/MPP-TPA-Article.Final.pdf?sequence=1&isAllowed=y https://www.utupub.fi/bitstream/handle/10024/164790/MPP-TPA-... ) Historically, the chance of such research turning into a chip you can buy is zero.
- systarray 2y agoSystolic processing, circa 1979. A concept that gets reinvented every decade: https://en.wikipedia.org/wiki/Systolic_array https://en.wikipedia.org/wiki/Systolic_array
- mikewarot 2y agoAnd it always gets prematurely optimized to fit a specific problem instead of being made general purpose compute engine. FPGAs are essentially horrible systolic arrays. They're lumpy, and have weird routing hardware that isn't easy to abstract out. Those lead to multiple day compile times in some cases. They don't pipeline things by default. The programming languages used are nowhere near a good fit to the hardware. It's just a mess. It happens every time.
- imtringued 2y agoSystolic arrays are only used for fixed function computing within the context of individual instructions, e.g. a matrix multiplication or convolution unit. In practice however, most of these arrays are wave front processors, because programmable processing elements can take variable amounts of time per stage and therefore become asynchronous. AMD's XDNA NPU is based around a wave front array of 32 compute tiles, each of which can either perform a 4x8 X 8x4 matrix multiplication in float16 or a 1024 bit vector operation per cycle.
- almostgotcaught 2y agoIt's funny how everyone in this thread is wrong on the high level concepts (blind leading the blind) but here you're wrong on the specifics too > around a wave front array of 32 compute tiles, each of which can either perform a 4x8 X 8x4 matrix multiplication in float16 or a 1024 bit vector operation per cycle. 1. XDNA is exactly the opposite of a "wavefront" processor. Each compute core is single thread vector VLIW. So you have X number of independent fixed function operators. 2. There is no XDNA product with 32 cores and 4x8x4 matmul. Phoenix has 20 compute cores (16 usable) and performs 4x8x4. Strix has 32 and performs 16x32x8 matmul.