分布式通讯优化篇 – IRQ affinity

      在一次C500K性能压测过程中，发现一个问题：8 processor的CPU，负载基本集中在CPU0，并且负载达到70以上，并通过mpstat发现CPU0每秒总中断（%irq+%soft）次数比较高。

      基于对此问题的研究，解决和思考，便有了这篇文章，希望大家能够喜欢，也欢迎大家留言讨论。

      在正文开始之前，我们先来看两个跟性能相关的基本概念：中断与上线文切换（在实际场景中，发现90%以上的同学说不清楚），希望这篇文章能带给你一些帮助，如果有疑问，欢迎交流。

      中断

        Hardware interrupts are used by devices to communicate that they require attention from the operating system. Internally, hardware interrupts are implemented using electronic alerting signals that are sent to the processor from an external device, which is either a part of the computer itself, such as a disk controller, or an external peripheral. For example, pressing a key on the keyboard or moving the mouse triggers hardware interrupts that cause the processor to read the keystroke or mouse position. Unlike the software type (described below), hardware interrupts are asynchronous and can occur in the middle of instruction execution, requiring additional care in programming. The act of initiating a hardware interrupt is referred to as an interrupt request (IRQ).

         A software interrupt is caused either by an exceptional condition in the processor itself, or a special instruction in the instruction set which causes an interrupt when it is executed. The former is often called a trap or exception and is used for errors or events occurring during program execution that are exceptional enough that they cannot be handled within the program itself. For example, if the processor's arithmetic logic unit is commanded to divide a number by zero, this impossible demand will cause a divide-by-zero exception, perhap