Searcharxiv⌕ Search
Home/Archive/arXiv

arXiv · 2608.14589

Comparing UPF Dataplane I/O Modes in a Cloud-Native 5G Core: AF_PACKET, AF_XDP, CNDP, and DPDK on SD-Core BESS-UPF

Shiva Valia·Nitin Rajput·Aditya Gairola·Vipin Rathi
View original source ↗Read source document ↗Export metadata ↓

Abstract

The User Plane Function (UPF) carries all user-plane traffic in a 5G network, and its throughput depends on how packets move between the NIC and the application, that is, on the packet I/O mode. We compare four widely used modes, AF_PACKET, AF_XDP, the Cloud Native Data Plane (CNDP), and the Data Plane Development Kit (DPDK), on a single open-source UPF. Using SD-Core BESS-UPF deployed as a Charmed operator on Intel XXV710 NICs in Canonical Kubernetes, we run the same GTP-U/PDR/FAR/QER pipeline under each mode and change only the BESS port driver, so any difference is attributable to the I/O backend. For each mode we describe its architecture, datapath, memory model, and deployment requirements, and we measure throughput, latency, CPU usage, and stability; the deployment is also validated end-to-end against a disaggregated O-RAN 5G RAN with a commercial UE. On an XXV710/i40e testbed (NDR per RFC 2544) at 64 B, AF_PACKET reaches 0.25 Mpps, CNDP 5.52 and AF_XDP 6.47 Mpps at 2 workers, and DPDK 10.30 Mpps at 4 workers and 13.09 at 8, with the lowest latency (8.1 microseconds average). At matched worker counts the three kernel-bypass modes are within noise and AF_XDP leads per core; DPDK's advantage is a scaling-ceiling effect, since its native PMD over vfio-pci escapes the per-netdev AF_XDP socket limit that pins CNDP and AF_XDP at two workers, not a per-packet efficiency win. CNDP and AF_XDP are the cloud-native sweet spot when hugepages, vfio-pci, and isolated cores are unaffordable; DPDK is justified on dedicated hosts. We also document deployment pitfalls absent from synthetic benchmarks, including a Kubernetes limits.cpu mis-setting that silently halved DPDK throughput. The paper is a side-by-side reference for operators choosing a UPF dataplane mode in a cloud-native 5G deployment.

Explore related subjects

cs.NIcs.CR

Keep this discovery

BibTeXRIS

Shiva Valia, Nitin Rajput, Aditya Gairola, Vipin Rathi. 2026-06-22. Comparing UPF Dataplane I/O Modes in a Cloud-Native 5G Core: AF_PACKET, AF_XDP, CNDP, and DPDK on SD-Core BESS-UPF. https://arxiv.org/abs/2608.14589

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related papers

arXiv2026

Message-Level Scheduling for RLNC-Coded Multi-Source Traffic

This paper studies weighted decoding-delay minimization for multiple RLNC-coded message streams that compete for finite processing capacity at a destination. Packet arrivals are exogenous, while the scheduler only determines the processing order of packets already available at the destination. A trace-conditioned offline scheduling formulation shows that a batch-release subclass is strongly NP-hard even with a single processing unit. Message-Aware Innovation-Deficit Scheduling (MAIDS) is then developed to prioritize each serviceable message according to its weight and remaining decoding deficit. For a single processing unit, MAIDS is shown to be exactly optimal under nonblocking progressive arrivals with equal weights and under common activation with arbitrary positive weights, while the unrestricted weighted online problem admits no universal deterministic $O(1)$ competitive ratio. Simulation results on streaming and batch benchmarks show that MAIDS consistently reduces weighted decoding delay relative to the tested baselines, remains close to the offline optimum on average, and recovers the predicted exact performance boundaries.

cs.NI↗
arXiv2026

The Towers Were Standing: A Cause Decomposition of Cellular Outages During Hurricane Helene

Hurricane Helene produced the largest absolute cell-site outage in the public FCC record, peaking at 4562 sites. The conventional model is physical: towers destroyed. Helene did destroy over 1700 miles of fibre, but almost none of it was cell sites. We present the first cause-decomposed study of the FCC's Disaster Information Reporting System, reconstructing 80 state-days and 580 county-days from 24 daily filings by two reconciled independent extractions. Damage to cell sites is negligible: 1.1% of attributed cell-site-days across six states, at most 3.8% anywhere. The sites were standing. What took them out divides by terrain: pooled, power dominates at 63.2%, but in mountainous North Carolina severed transport (backhaul) reaches 52.2% against 47.3%, and in Tennessee 69.9%. North Carolina's transport share rises from 7.0% to 85.0% across the event (\r{ho} = 0.92). Seventeen days after landfall, on 15 October, 47 sites lost transport across six contiguous North Carolina counties with no rainfall, no power loss, no damage, and recovery by the next report. Independent active-probe measurement corroborates it: responsive /24s fall 1.02% for twelve hours while Tennessee stays flat. We release the dataset. Backup power is the standard resilience investment; here it addresses the smaller half of the problem.

cs.NI↗
arXiv2026

terms.txt: A Consent and Compensation Protocol for Agentic Web Access

The open web ran on an unwritten bargain: sites admitted crawlers, and search engines sent visitors back. Public measurements show that bargain breaking under AI crawlers and agents. Automated clients now make up most requests, training dominates Cloudflare-classified crawling, and the largest AI platforms fetch thousands of pages for each visitor they return. The web's common control, robots.txt, cannot express identity, purpose, terms, or price, can be circumvented, and newer alternatives are largely proprietary CDN features. We specify terms.txt, a robots.txt-style file for per-path, per-purpose machine-access terms, plus an origin-enforced exchange using Web Bot Auth signatures, signed intent, delegation tokens, HTTP 402 negotiation, and signed receipts. We define what the exchange can enforce, audit, and leave to contract. A dependency-free implementation adds 0.20 to 0.65 ms per request on one vCPU.

cs.NI↗