PHY? Yeah, that's totally different.

Modern cars are switching from CAN bus to Ethernet for talking between modules. 100baseT1 is a common flavor that runs Ethernet frames at 100 Mbps bidirectionally over a single pair of wires.

If you want to simultaneously look at a protocol decode and signal quality view of that signal in both directions you're looking at around a GB/s of data. Which ngscopeclient is able to crunch in real time (barely, this is a recent tech demo)

Even USB 3.0 was 5 Gbps per pair and that's pretty slow compared to modern stuff. PCIe gen6 runs at 64 Gbps.

DisplayPort goes up to 20 Gbps per lane now.

But understanding complex issues around these buses involves recording a lot of data, processing it fast, looking at packet captures and physical layer signal quality, etc. There's always room to crunch more data faster.

Until then I'm stuck with what I can get my hands on. Realistically, that's PCIe and RoCE

But the second part about the thunderscope is cool.

But it still has to cross over PCIe and get bottlenecked on that bandwidth

But Ethernet today tops out at 800 Gbps while the latest NVLink can do 14.4 Tbps

but I can dream...

equally, a scope that acquires high speed data and buffers it in memory before processing at a much slower rate is something we can handle today.

But the vision is to be able to do real time or at least lower-dead-time processing at much higher data rates. ThunderScope almost maxes out 10GbE, my vision is to able to keep up with 25/40/100G eventually

And the nic has RoCE offload capabilities although I'm not using it yet

Realistically, I think the best you can do portably today is 100GbE with RoCE.

That's 160 GB/s or 1.28 Tbps of raw samples.

That would even fit in NVLink 2.0 much less the current gen4/5 stuff.

Imagine four channels of 16 GHz bandwidth waveform data straight into a (very large) GPU nonstop... We'd have to do a hell of a lot of optimization to ngscopeclient to keep up and probably add multi-GPU support but it would be so much fun lol.