You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In various cases, a network interface may only have a single hardware queue.
While this is not a problem in itself, if you are researching low network performance or dropped packets its a likely contributor. We should surface this as a "note" (but not an error). e.g. interface X has a single hardware queue, this may limit network performance or caused dropped packets during traffic bursts.
You will have a file for each hardware queue, e.g. rx-0, rx-1, rx-2
Also related is that you can improve this by setting the mask in /sys/class/net/IFACE/rx-*/{rps,xps}_cpus - we should perhaps surface the current value of that as well.
The text was updated successfully, but these errors were encountered:
In various cases, a network interface may only have a single hardware queue.
While this is not a problem in itself, if you are researching low network performance or dropped packets its a likely contributor. We should surface this as a "note" (but not an error). e.g. interface X has a single hardware queue, this may limit network performance or caused dropped packets during traffic bursts.
Places that will report this (may be more):
/sys/class/net/INTERFACE/queues/{rx,tx}-*/
You will have a file for each hardware queue, e.g. rx-0, rx-1, rx-2
Also related is that you can improve this by setting the mask in
/sys/class/net/IFACE/rx-*/{rps,xps}_cpus
- we should perhaps surface the current value of that as well.The text was updated successfully, but these errors were encountered: