3 ms·
My personal use case was for hard realtime requirements. For example, burning electronic fuses in an ASIC, where timing had to be guaranteed or the chip was to
by nomel 8y ago
My personal use case was for hard realtime requirements.
For example, burning electronic fuses in an ASIC, where timing had to be guaranteed or the chip was toast.
Beyond that, like most have said, bit banging odd protocols at reasonable speed, with full access to main memory for streaming.
For a funny optimization that resulted in lower performance: I offloaded one of our protocols to one of these coprocessors but noticed the overall throughput dropped to about 1/4 what it was before, with huge latency between transactions. I looked at the cpu and, as was the goal, main processor usage was down from 30% to about 2%. I eventually realized that, due to the low CPU usage, the main processor clock rate was scaled to the lowest frequency. This caused interrupt handling, and everything else, to slow wayyy down, including the arbiter in the kernel driver and user space code where the transactions were coming from.
The fix was to disable clock scaling completely, burning some watts more. I’m sorry dolphins :(