Documentation
¶
Overview ¶
sweep drives every backend through the same three loops -- transmit, receive, forward -- so a comparison between them measures the backend and not four different programs.
sweep -io mlx5 -i eno2 -mode tx -queues 4 -cpus 0-3 sweep -io dpdk -i 0000:c1:00.1 -mode rx -queues 8 -cpus 0-7 sweep -io afxdp -i eno2 -mode fwd -queues 2 -cpus 0-1 sweep -io afpacket -i eno2 -mode tx -queues 1
It prints one RESULT line with what the application counted. The authoritative rate for a benchmark is the port's own counters, read by the harness around the measurement window; this count is the cross-check.
mlx5 and dpdk need their build tags; without them those two backends are simply not registered:
go build -tags "mlx5 dpdk" ./examples/sweep
Click to show internal directories.
Click to hide internal directories.