Metraipolis › archive › dc_4f5294d2db57
LatencyLab: A DPDK-Based P4 Pipeline Latency Measurement Framework for FPGA SmartNICs — arXiv:2609.39978
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2609.39978
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-07T13:14:57.629Z
- SHA-256 of the archived text
2172771f14adc2fb50089ae8197ad5cb9a396f126ae23c184a3d6da4a0ee7533- Stable URL of this page
https://metraipolis.com/documento/dc_4f5294d2db57
How to cite
LatencyLab: A DPDK-Based P4 Pipeline Latency Measurement Framework for FPGA SmartNICs — arXiv:2609.39978 — arXiv (en), https://arxiv.org/abs/2609.39978 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_4f5294d2db57 (Metraipolis archive dc_4f5294d2db57, sha256 2172771f14adc2fb50089ae8197ad5cb9a396f126ae23c184a3d6da4a0ee7533)
BibTeX
@misc{dc4f5294d2db57,
title = {LatencyLab: A DPDK-Based P4 Pipeline Latency Measurement Framework for FPGA SmartNICs — arXiv:2609.39978},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2609.39978},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_4f5294d2db57; sha256 2172771f14adc2fb50089ae8197ad5cb9a396f126ae23c184a3d6da4a0ee7533},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.39978. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
P4-programmable FPGA SmartNICs place packet processing directly on the wire, but open FPGA P4 toolflows do not expose timestamping at the pipeline boundary, so the latency a P4 program adds on the target FPGA is rarely measured. This paper presents LatencyLab, a DPDK-based measurement framework for FPGA P4 pipeline latency that needs neither PHC/PTP support on the datapath nor clock synchronization. The FPGA's two ports share a network segment, so the switch multicasts a copy of each probe packet to both: one copy passes through the VitisNetP4 pipeline, the other through a matched bypass path. A kernel-bypass DPDK receiver busy-polls both ports and timestamps every packet with the CPU timestamp counter (TSC) as it is retrieved from the NIC's receive circular buffer. The arrival-time difference of the two copies isolates the pipeline latency after calibration against a null bitstream carrying the same traffic; transmit time cancel in the subtraction. We evaluate four VitisNetP4 programs on an AMD Alveo U280, probing each with a 20,000-packet trace measured ten times per session over five independent sessions, all TSC-timestamped and reflected for hardware timestamping. The measured latency distributions are tight and reproducible: 99% of packets fall within 20 ns of the median, session medians repeating within 1 to 2 ns (FiveTuple 107/137 ns, Forward 149 ns, RemoveHeader 177 ns, Checksum 364 ns at 250 MHz). Two independent checks agree with the framework: a kernel-free reflector returns every probe pair to a ConnectX-5 NIC whose adapter clock reproduces the measured distributions within a few nanoseconds, quantile by quantile, and every measured packet falls 18 to 22 clock cycles below the vendor's worst-case latency bound. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-10-01 in cs.DC). Categorie arXiv: Distributed, Parallel, and Cluster Computing (cs.DC). Pagina del lavoro: https://arxiv.org/abs/2609.39978 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-07T12:46:39.738Z dalla pagina https://arxiv.org/catchup/cs.DC/2026-10-01?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).