Receive Side Scaling: Difference between revisions
No edit summary Tags: Mobile edit Mobile web edit |
No edit summary Tags: Mobile edit Mobile web edit |
||
| Line 2: | Line 2: | ||
<tt>irqbalance</tt> works by identifying large interrupt sources, and binding their handlers to different processors. Under this scheme, a single NIC's traffic will only be handled on a single CPU. With sufficiently high loads, we need handling on multiple CPUs. RSS is typically configured so that all packets of a given flow go to a single CPU, and different flows are randomly distributed across CPUs. Each receive queue gets its own IRQ, which can then be directed to a set of CPUs via standard processes. <tt>irqbalance</tt> can conflict with manual RSS configurations. | <tt>irqbalance</tt> works by identifying large interrupt sources, and binding their handlers to different processors. Under this scheme, a single NIC's traffic will only be handled on a single CPU. With sufficiently high loads, we need handling on multiple CPUs. RSS is typically configured so that all packets of a given flow go to a single CPU, and different flows are randomly distributed across CPUs. Each receive queue gets its own IRQ, which can then be directed to a set of CPUs via standard processes. <tt>irqbalance</tt> can conflict with manual RSS configurations. | ||
==ethtool== | |||
* <tt>--show-ntuple</tt>: | |||
==Links== | ==Links== | ||
* Microsoft [https://docs.microsoft.com/en-us/windows-hardware/drivers/network/introduction-to-receive-side-scaling RSS docs] under "Driver Technologies" | * Microsoft [https://docs.microsoft.com/en-us/windows-hardware/drivers/network/introduction-to-receive-side-scaling RSS docs] under "Driver Technologies" | ||