From: Rick Jones <rick.jones2@hpe.com>
To: netdev@vger.kernel.org
Cc: sathya.perla@broadcom.com, ajit.khaparde@broadcom.com,
sriharsha.basavapatna@broadcom.com, somnath.kotur@broadcom.com
Subject: Re: A second case of XPS considerably reducing single-stream performance
Date: Wed, 24 Aug 2016 16:46:22 -0700 [thread overview]
Message-ID: <a661ff61-9cf8-fe86-ca20-2181394e1dbb@hpe.com> (raw)
In-Reply-To: <549357ea-dfda-284b-cdd6-4408060f9ca8@hpe.com>
Also, while it doesn't seem to have the same massive effect on
throughput, I can also see out of order behaviour happening when the
sending VM is on a node with a ConnectX-3 Pro NIC. Its driver is also
enabling XPS it would seem. I'm not *certain* but looking at the traces
it appears that with the ConnectX-3 Pro there is more interleaving of
the out-of-order traffic than there is with the Skyhawk. The ConnectX-3
Pro happens to be in a newer generation server with a newer processor
than the other systems where I've seen this.
I do not see the out-of-order behaviour when the NIC at the sending end
is a BCM57840. It does not appear that the bnx2x driver in the 4.4
kernel is enabling XPS.
So, it would seem that there are three cases of enabling XPS resulting
in out-of-order traffic, two of which result in a non-trivial loss of
performance.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2016-08-25 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 15:52 A second case of XPS considerably reducing single-stream performance Rick Jones
2016-08-24 23:46 ` Rick Jones [this message]
2016-08-25 19:19 ` Alexander Duyck
2016-08-25 20:18 ` Rick Jones
2016-08-25 20:44 ` Alexander Duyck
2016-08-25 21:02 ` Tom Herbert
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=a661ff61-9cf8-fe86-ca20-2181394e1dbb@hpe.com \
--to=rick.jones2@hpe.com \
--cc=ajit.khaparde@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=sathya.perla@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox