From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: Remote checksum offload for VXLAN
Date: Tue, 25 Nov 2014 13:50:38 -0500 (EST) [thread overview]
Message-ID: <20141125.135038.450259284061493243.davem@davemloft.net> (raw)
In-Reply-To: <1416873150-12260-1-git-send-email-therbert@google.com>
From: Tom Herbert <therbert@google.com>
Date: Mon, 24 Nov 2014 15:52:27 -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
>
> Tested by running 200 TCP_STREAM connections with VXLAN (over IPv4).
What to do with the reserved bit seems to still be up in the air,
so I've marked this series as 'deferred'.
prev parent reply other threads:[~2014-11-25 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 23:52 [PATCH net-next 0/3] net: Remote checksum offload for VXLAN Tom Herbert
2014-11-24 23:52 ` [PATCH net-next 1/3] net: Add remcsum_adjust as common function for remote checksum offload Tom Herbert
2014-11-24 23:52 ` [PATCH net-next 2/3] gue: Call remcsum_adjust Tom Herbert
2014-11-24 23:52 ` [PATCH net-next 3/3] vxlan: Remote checksum offload Tom Herbert
2014-11-25 1:06 ` Jesse Gross
2014-11-25 2:50 ` Tom Herbert
2014-11-25 18:54 ` Jesse Gross
2014-11-25 18:50 ` 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=20141125.135038.450259284061493243.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).