Optimize network interrupt handling on Arm servers
Introduction
Understand and analyze network IRQ configuration
IRQ management patterns for performance optimization
Conclusion and recommendations
Next Steps
Optimize network interrupt handling on Arm servers
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Restore the default IRQ handling by running
sudo systemctl unmask irqbalance and sudo systemctl enable --now irqbalance. If irqbalance isn’t installed on a Debian-based system, install it with sudo apt install irqbalance.Start by concentrating network IRQs on one or two CPU cores instead of spreading them across all cores. Use the
smp_affinity range assignment recommended in the path to bind the interrupts.You should see NIC interrupts bound to the cores that you selected, and a consistent distribution under network load. Compare the new layout to your baseline to confirm that the change took effect.
IRQ changes reset at reboot. Add your affinity settings to
/etc/rc.local or create a systemd service file so that the assignments are reapplied when the system starts.Switch to an alternative distribution strategy and retest, because effectiveness depends on workload and system size. No single approach is optimal everywhere, so iterate and validate under representative load.