From: Tom Herbert <tom@herbertland.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <kernel-team@fb.com>
Subject: [PATCH net-next v2 0/3] geneve: Add support for Remote Checksum Offload
Date: Thu, 10 Dec 2015 12:34:30 -0800 [thread overview]
Message-ID: <1449779673-3701191-1-git-send-email-tom@herbertland.com> (raw)
This patch set adds UDP checksum configuration via netlink and
Remote Checksum Offload for Geneve,
v2:
- Fix issue of taking sizeof a pointer instead of the actual object
- Fix type in commi log
Testing (10Gbps mlx4):
Single connection TCP_STREAM in netperf
- No UDP checksums, no RCO
4371.9 Mbpos
- UDP checksums enabled, no RCO
7263.4 Mbps
- UDP checksums enabled, RCO enabled
7607.6 Mbps
200 TCP_RR streams
- No UDP checksums, no RCO
55.05% CPU utilization
879284.9 tps
184/231/742 50/90/99% latencies
- UDP checksums enabled, no RCO
55.46% CPU utilization
901785 tps
176/222/738 50/90/99% latencies
- UDP checksums enabled, RCO enabled
52.36% CPU utilization
910582 tps
174/218/706 50/90/99% latencies
Tom Herbert (3):
rco: Clean up casting errors
geneve: UDP checksum configuration via netlink
geneve: Remote Checksum Offload support
drivers/net/geneve.c | 249 ++++++++++++++++++++++++++++++++++++++-----
include/net/checksum.h | 3 +-
include/net/geneve.h | 22 +++-
include/uapi/linux/if_link.h | 6 ++
4 files changed, 246 insertions(+), 34 deletions(-)
--
2.4.6
next reply other threads:[~2015-12-10 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 20:34 Tom Herbert [this message]
2015-12-10 20:34 ` [PATCH net-next v2 1/3] rco: Clean up casting errors Tom Herbert
2015-12-10 20:34 ` [PATCH net-next v2 2/3] geneve: UDP checksum configuration via netlink Tom Herbert
2015-12-10 20:34 ` [PATCH net-next v2 3/3] geneve: Remote Checksum Offload support Tom Herbert
2015-12-14 4:59 ` [PATCH net-next v2 0/3] geneve: Add support for Remote Checksum Offload David Miller
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=1449779673-3701191-1-git-send-email-tom@herbertland.com \
--to=tom@herbertland.com \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--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).