Strategies for Rate Limiting Network Packet Ingress
summary
Shows three concrete ingress rate‑limit implementations and measured effects: using tc qdisc to drop to 10 Mbps and reduce CPU from ~95% to ~4% (but requires restarting the flow to apply), using eBPF/XDP at the driver to drop to <10 Mbps and cut CPU to ~1% (requires XDP-capable driver and kernel BPF config), and using ethtool to force PHY to 10 Mbps (no intentional drops, CPU ~5%, link goes down/up and limited to fixed speeds).
AI-written summary · about
chapters (9)
- 0:00Network storms and rate limiting
- 3:40Storm control for packet ingress
- 5:45Rate limiting methods
- 6:06TC utility for ingress
- 15:47eBPF for packet filtering
- 24:17Ethernet link speed adjustment
- 28:57Performance vs configurability
- 32:32Key takeaways and hardware
- 33:58Conclusion and Q&A
related talks
16mR-TCP: A Framework to Optimize TCP Performance Over Rate-Limiting Networks
53mWhat is eating my traffic? Packet thieves revealed
07mLightning Talk: Taming Noisy Network Neigbours with Cilium and eBPF
30mNicPic: Scalable and Accurate End-Host Rate Limiting
19mTackling DC Congestion and Bursts
17mEnabling Users to Control their Internet
22mLIVE Q&A #3
28mSafe sharing of the network with eBPF