netdev - Re: Disabling XPS for 4.4.0-1+ixgbe+OpenStack VM over a VLAN means 65% increase in netperf TCP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 4 Feb 2016 12:28:09 -0800
From:	Rick Jones <rick.jones2@....com>
To:	Tom Herbert <tom@...bertland.com>
Cc:	Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: Disabling XPS for 4.4.0-1+ixgbe+OpenStack VM over a VLAN means
 65% increase in netperf TCP_STREAM

On 02/04/2016 12:13 PM, Tom Herbert wrote:
> On Thu, Feb 4, 2016 at 11:57 AM, Rick Jones <rick.jones2@....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