From: Rick Jones <rick.jones2@hpe.com>
To: Tom Herbert <tom@herbertland.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Disabling XPS for 4.4.0-1+ixgbe+OpenStack VM over a VLAN means 65% increase in netperf TCP_STREAM
Date: Thu, 4 Feb 2016 12:28:09 -0800 [thread overview]
Message-ID: <56B3B459.5040204@hpe.com> (raw)
In-Reply-To: <CALx6S37CekHutCQaXacpqKMSag971_GnHBZQTSE-DwU1tbt1RA@mail.gmail.com>
On 02/04/2016 12:13 PM, Tom Herbert wrote:
> On Thu, Feb 4, 2016 at 11:57 AM, Rick Jones <rick.jones2@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
next prev parent reply other threads:[~2016-02-04 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 19:13 Disabling XPS for 4.4.0-1+ixgbe+OpenStack VM over a VLAN means 65% increase in netperf TCP_STREAM Rick Jones
2016-02-04 19:38 ` Tom Herbert
2016-02-04 19:57 ` Rick Jones
2016-02-04 20:13 ` Tom Herbert
2016-02-04 20:28 ` Rick Jones [this message]
2016-02-08 18:03 ` Rick Jones
2016-02-08 19:03 ` Rick Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B3B459.5040204@hpe.com \
--to=rick.jones2@hpe.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.