Understanding Host Network Stack Latency
TL;DR
The root causes of tail latency in the Linux network stack are studied and it is suggested that achieving low-latency networking requires rethinking host CPU scheduling and host-NIC interaction, providing new design directions for operating systems, network stacks, and future host networking hardware.
Abstract
One of the most frequently cited flaws of Linux host network stacks is their high latency—recent studies show that the Linux network stack suffers from millisecond-scale tail latency. This has motivated clean-slate solutions such as userspace stacks and specialized host networking hardware, but without understanding the true root causes of Linux tail latency, these efforts risk repeating the same pitfalls. This paper studies the root causes of tail latency in the Linux network stack and reaches a surprising conclusion: the dominant bottlenecks lie not in packet processing itself, but in how the host manages CPU resources for networking. Through extensive measurements, we identify three key factors: misattribution of processing time by CPU schedulers, limitations of CPU runtime as a fairness abstraction, and the inefficiency of interrupt tuning under unpredictable packet arrivals. We show that addressing these factors improves performance by up to 5.3× while maintaining similar throughput. Together, these results suggest that achieving low-latency networking requires rethinking host CPU scheduling and host-NIC interaction, providing new design directions for operating systems, network stacks, and future host networking hardware.