Network & Infrastructure / Linux Networking & Host Performance
Softnet backlog drops before application delivery
A packet-rate workload drops traffic even though interface error counters stay clean. The kernel's receive processing queues can overflow after packets have passed the NIC.
Environment and inputs: Linux network namespaces, host routing and network drivers; availability and semantics depend on kernel and driver versions. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Collect softnet statistics, per-CPU softirq load, NIC ring drops and application receive rates over the same interval. Distinguish hardware receive loss from later software backlog pressure.
Explain the result
Different stages have different counters and resource limits. A clean physical interface does not prove that the kernel can process the arrival rate or that the application can drain its socket.
Plan the fix
Address queue distribution and processing capacity before increasing backlog limits. Bound the latency and memory consequences of buffering rather than treating larger queues as free packet-loss prevention.
Check the result and rollback
Measure drops at each stage and application tail latency under peak packet rates. Restore prior limits if added buffering masks overload while increasing response time beyond the service objective.