netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Herbert <therbert@google.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Subject: [PATCH net-next v2 0/2] net: Remote checksum offload for VXLAN
Date: Mon, 12 Jan 2015 17:00:36 -0800	[thread overview]
Message-ID: <1421110838-5146-1-git-send-email-therbert@google.com> (raw)

This patch set adds support for remote checksum offload in VXLAN.

The remote checksum offload is generalized by creating a common
function (remcsum_adjust) that does the work of modifying the
checksum in remote checksum offload. This function can be called
from normal or GRO path. GUE was modified to use this function.

To support RCO is VXLAN we use the 9th bit in the reserved
flags to indicated remote checksum offload. The start and offset
values are encoded n a compressed form in the low order (reserved)
byte of the vni field.

Remote checksum offload is described in
https://tools.ietf.org/html/draft-herbert-remotecsumoffload-01

Changes in v2:
  - Add udp_offload_callbacks which has GRO functions that take a
    udp_offload pointer argument. This argument can be used to retrieve
    a per port structure of the encapsulation for use in gro processing
    (mostly by doing container_of on the structure).
  - Use the 10th bit in VXLAN flags for RCO which does not seem to
    conflict with other proposals at this time (ie. VXLAN-GPE and
    VXLAN-GPB)
  - Require that RCO must be explicitly enabled on the receiver
    as well as the sender.

Tested by running 200 TCP_STREAM connections with VXLAN (over IPv4).

With UDP checksums and Remote Checksum Offload
  IPv4
      Client
        11.84% CPU utilization
      Server
        12.96% CPU utilization
      9197 Mbps
  IPv6
      Client
        12.46% CPU utilization
      Server
        14.48% CPU utilization
      8963 Mbps

With UDP checksums, no remote checksum offload
  IPv4
      Client
        15.67% CPU utilization
      Server
        14.83% CPU utilization
      9094 Mbps
  IPv6
      Client
        16.21% CPU utilization
      Server
        14.32% CPU utilization
      9058 Mbps
 
No UDP checksums
  IPv4
      Client
        15.03% CPU utilization
      Server
        23.09% CPU utilization
      9089 Mbps
  IPv6
      Client
        16.18% CPU utilization
      Server
        26.57% CPU utilization
       8954 Mbps

Tom Herbert (2):
  udp: pass udp_offload struct to UDP gro callbacks
  vxlan: Remote checksum offload

 drivers/net/vxlan.c          | 198 +++++++++++++++++++++++++++++++++++++++++--
 include/linux/netdevice.h    |  15 +++-
 include/net/vxlan.h          |  11 +++
 include/uapi/linux/if_link.h |   2 +
 net/ipv4/fou.c               |  12 ++-
 net/ipv4/geneve.c            |   6 +-
 net/ipv4/udp_offload.c       |   7 +-
 7 files changed, 233 insertions(+), 18 deletions(-)

-- 
2.2.0.rc0.207.ga3a616c

             reply	other threads:[~2015-01-13  1:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13  1:00 Tom Herbert [this message]
2015-01-13  1:00 ` [PATCH net-next v2 1/2] udp: pass udp_offload struct to UDP gro callbacks Tom Herbert
2015-01-13  1:00 ` [PATCH net-next v2 2/2] vxlan: Remote checksum offload Tom Herbert
2015-01-13  1:26   ` Thomas Graf
2015-01-13 11:44     ` Thomas Graf
2015-01-13 16:40       ` Thomas Graf
2015-01-13 17:26         ` Tom Herbert
2015-01-14 20:21 ` [PATCH net-next v2 0/2] net: Remote checksum offload for VXLAN 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=1421110838-5146-1-git-send-email-therbert@google.com \
    --to=therbert@google.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).