From: Alexander Duyck <aduyck@mirantis.com>
To: netdev@vger.kernel.org, davem@davemloft.net, alexander.duyck@gmail.com
Subject: [net-next PATCH 0/2] Prevent packet reordering on tap/tun interfaces
Date: Wed, 01 Jun 2016 18:17:11 -0700 [thread overview]
Message-ID: <20160602010741.9319.56926.stgit@localhost.localdomain> (raw)
This patch set is meant to address a recent issue I found with VMs sending
traffic across a network. Specifically what I found was that the tap
interfaces were spreading single flows across all CPUs on the system due
to the fact that the sending VM was being load balanced across them. Under
light load this doesn't have much of an impact, however under heavier loads
where the interfaces are already running with Rx cleanup from other flows
on the CPUs I have seen this have a fairly significant impact as we can
avoid any issues due to reordering. The results can be anywhere from 10 to
30% improvement from what I have seen.
---
Alexander Duyck (2):
net: Add function to allow configuration of RPS
tun: Configure Rx queues to default to RPS enabled
drivers/net/tun.c | 4 +++-
include/linux/netdevice.h | 9 ++++++++
net/core/dev.c | 51 ++++++++++++++++++++++++++++++++++++++++++++-
net/core/net-sysfs.c | 45 +++++++---------------------------------
4 files changed, 70 insertions(+), 39 deletions(-)
next reply other threads:[~2016-06-02 1:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 1:17 Alexander Duyck [this message]
2016-06-02 1:17 ` [net-next PATCH 1/2] net: Add function to allow configuration of RPS Alexander Duyck
2016-06-02 1:23 ` Alexander Duyck
2016-06-02 1:17 ` [net-next PATCH 2/2] tun: Configure Rx queues to default to RPS enabled Alexander Duyck
2016-06-02 13:12 ` Eric Dumazet
2016-06-02 15:24 ` Alexander Duyck
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=20160602010741.9319.56926.stgit@localhost.localdomain \
--to=aduyck@mirantis.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).