New answers tagged packet
I had a similar (?) challenge on a Red Hat Enterprise Linux box. I read the same paper, and concluded that my real problem was that the default of using every possible IRQ to get every CPU involved in network packet work. I focused the IRQ activity to a subset of available cores and then steered work accordingly. Here's the rc.local file: # Reserve CPU0 ...
Top 50 recent answers are included