3 ms·
That's either a big waste of silicon or a very hard problem. On a related topic, I know someone who worked on CPU/FPGA hybrid architectures. The idea was to mo
by GuB-42 9y ago
That's either a big waste of silicon or a very hard problem.
On a related topic, I know someone who worked on CPU/FPGA hybrid architectures. The idea was to move processes between CPUs and FPGAs. Awesome stuff, realtime processes offloaded to the FPGA get to run completely off the CPU, with ridiculously low latencies. The issue is that you really have to design your code for it.
- nine_k 9y agoFPGAs are great because they are field-programmable and can adapt the hardware to a task. In all other aspects (density, power draw, cost) they are not that great. We could consider something like Tilera chips working together with privileged "general compute" chips, the same way as current machines work with separate GPUs as privilege "vector compute" chips.
- milesvp 9y agoI still dream of a day where the compiler largely handles this kind of thing for you. I'm starting to suspect that this day may never come, but it feels like a logical extension of the jit. To have code that self modifies not just itself to run faster, but also the hardware it runs on just seems so cool. Course, in the context of the larger thread, I can't help but wonder how much more attack surface this would tend to create.
- qubex 9y agoI remember something marketed as a “hypercomputer” by Starburst Systems or something like that (long since defunct, apparently... I'm referring back to the late 1990s and early 2000s) that “compiled software to hardware” by substituting parallel CPUs with FPGAs.
- Aloha 9y agoThis approach has been tried - as it turns out, we're not very good at writing compilers.
- zzzcpan 9y agoCompilers are sort of at the edge of technology, there is always some value in trying again, no matter how many times it has been tried before.
- phkahler 9y ago>> That's either a big waste of silicon or a very hard problem. How about 16 big core and 4096 small cores that don't have speculative execution? https://content.riscv.org/wp-content/uploads/2017/12/Tue1136-Industrial-Strength-High-Performance-RISC-V-Processors-for-Energy-Efficient-Computing-Ditzel-Esperanto.pdf https://content.riscv.org/wp-content/uploads/2017/12/Tue1136... Perhaps one day we'll talk about how many cores are allocated to a program rather than the other way around. OTOH even their chip will have shared caches. Spectre is achieved via speculation but communicates via side channel of the cache, so it's not clear this is a whole lot better.
- warkdarrior 9y agoThere are always things that are shared even between distinct cores: RAM, buses, disk I/O, network I/O, LAN, the Internet, etc.
- phkahler 9y agoAgreed. I pointed out caches. Running only a single process per core does prevent sharing of the branch predictor and the lowest level cache. What nobody wants to say is that the real problem is running untrusted code. They don't want to say it because Apps and JS are so many peoples bread an butter these days.