On 02/04/2016 12:13 PM, Tom Herbert wrote:
On Thu, Feb 4, 2016 at 11:57 AM, Rick Jones <rick.jon...@hpe.com> wrote:
On 02/04/2016 11:38 AM, Tom Herbert wrote:
XPS has OOO avoidance for TCP, that should not be a problem.
What/how much should I read into:
With XPS TCPOFOQueue: 78206
Without XPS TCPOFOQueue: 967
out of the netstat statistics on the receiving VM?
Okay, that makes sense. The OOO avoidance only applies to TCP sockets
in the stack, that doesn't cross into VM. Presumably, packets coming
from the VM don't have a socket so sk_tx_queue_get always returns -1
and so netdev_pick_tx will steer packet to the queue based on
currently running CPU without any memory.
Any thoughts as to why explicitly binding the IRQs made things better,
or for that matter why the scheduler would be moving the VM (or its
vhost-net kernel thread I suppose?) around so much?
happy benchmarking,
rick jones
