From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: Remote checksum offload for VXLAN
Date: Wed, 14 Jan 2015 15:21:29 -0500 (EST) [thread overview]
Message-ID: <20150114.152129.1086585159807498251.davem@davemloft.net> (raw)
In-Reply-To: <1421110838-5146-1-git-send-email-therbert@google.com>
From: Tom Herbert <therbert@google.com>
Date: Mon, 12 Jan 2015 17:00:36 -0800
> 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
Tom's arguments for why he separates RX and TX paths seem completely
reasonable, and match my own understanding of the various tunneling
technologies we support.
Therefore, series applied, thanks!
prev parent reply other threads:[~2015-01-14 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 1:00 [PATCH net-next v2 0/2] net: Remote checksum offload for VXLAN Tom Herbert
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 ` David Miller [this message]
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=20150114.152129.1086585159807498251.davem@davemloft.net \
--to=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).