3 ms·
I've done some systolic processors on Xilinx hardware. It's really dang hard, on their biggest, fanciest chips, to pump the DSPs at anything close to their adv
by klyrs 6y ago
I've done some systolic processors on Xilinx hardware. It's really dang hard, on their biggest, fanciest chips, to pump the DSPs at anything close to their advertised clock speeds. Maybe if I was smarter, I could do an asynchronous design that would somehow avoid clocking issues, but I suspect that doing async between mismatched clock regions would effectively halve the clock (and that might be optimistic).
The only consolation for me is that I/O over PCI ends up being my ultimate bottleneck. If AMD did a full-on integration with their infinity fabric, it could actually be a game changer. For me, in my weirdo niche.
- dragontamer 6y agoI'm pretty sure I/O over PCIe is a substantial bottleneck in many applications (which is part of the reason for the 300GB/s POWER9 / OpenCAPI / NVLink / GPUs). Its a shame that NVLink is isolated to pretty much the DGX-line of computers and POWER9 (The "big" ones too, I don't think Talos II supports NVLink). But I guess an interconnect that fast will require dedicated, non-standard hardware. ---------- AMD's GPU Infinity Fabric seems to be a different infinity fabric from their CPU. CPU Infinity Fabric is ~50GB/s, but the GPU Infinity Fabric is GPU-to-GPU links of ~90GB/s. Realistically, PCIe 4.0 and 5.0 will be the path forward for standard PCs. There will always be incredible application-specific solutions (such as NVLink / NVSwitch on the DGX), but the general computer user will wait for the open standards to support such speeds before adopting them. At the moment, GPU-to-GPU communications probably will scale better than CPU-to-GPU comms. CPUs just aren't built for the bandwidth (outside of POWER9 / POWER10).