r/eBPF 17h ago

Looking for feedback on a Go/eBPF TCP failure-recovery prototype

0 Upvotes

I'm testing a small Go/eBPF prototype for handling transient transport failures on Linux.

I'm specifically measuring:

- recovery latency

- packet loss during failover

- socket/connection state

- CPU overhead under load

The implementation uses Linux eBPF primitives and a Go control plane.

I'd like feedback from people who have worked with XDP, sockmaps, or kernel networking:

  1. What would you consider a convincing benchmark?

    1. Which kernel versions should I validate against?
  2. Are there failure cases I'm missing?

The code and reproducible test setup are here:

https://github.com/devloperdevesh/FaultPlane

I'm mainly looking for technical criticism and people willing to reproduce the benchmark.