public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Tom Herbert <therbert@google.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 2/4] vxlan: Add support for remote checksum offload
Date: Thu, 5 Feb 2015 10:54:09 -0800	[thread overview]
Message-ID: <20150205105409.68ddcb96@urahara> (raw)
In-Reply-To: <1422550321-30901-3-git-send-email-therbert@google.com>

On Thu, 29 Jan 2015 08:51:59 -0800
Tom Herbert <therbert@google.com> wrote:

> This patch adds support to remote checksum checksum offload
> to VXLAN. This patch adds remcsumtx and remcsumrx to ip vxlan
> configuration to enable remote checksum offload for transmit
> and receive on the VXLAN tunnel.
> 
> https://tools.ietf.org/html/draft-herbert-vxlan-rco-00
> 
> Example:
> 
> ip link add name vxlan0 type vxlan id 42 group 239.1.1.1 dev eth0 \
>     udpcsum remcsumtx remcsumrx
> 
> Signed-off-by: Tom Herbert <therbert@google.com>

Does not apply to current iproute2 net-next branch because
the vxlan group policy extensions was applied first.

Please fix conflicts and resubmit.

  reply	other threads:[~2015-02-05 18:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 16:51 [PATCH iproute2 0/4] iproute: Support for remote checksum offload Tom Herbert
2015-01-29 16:51 ` [PATCH iproute2 1/4] ip link: Add support for remote checksum offload to IP tunnels Tom Herbert
2015-02-05 18:51   ` Stephen Hemminger
2015-01-29 16:51 ` [PATCH iproute2 2/4] vxlan: Add support for remote checksum offload Tom Herbert
2015-02-05 18:54   ` Stephen Hemminger [this message]
2015-01-29 16:52 ` [PATCH iproute2 3/4] iproute: Description of new options for VXLAN in ip-link man pages Tom Herbert
2015-01-29 17:20   ` Nikolay Aleksandrov
2015-02-05 18:55   ` Stephen Hemminger
2015-01-29 16:52 ` [PATCH iproute2 4/4] iproute: Descriptions of fou and gue options " Tom Herbert
2015-02-05 18:56   ` Stephen Hemminger

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=20150205105409.68ddcb96@urahara \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    --cc=therbert@google.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