From: David Miller <davem@davemloft.net>
To: aduyck@mirantis.com
Cc: tom@herbertland.com, alexander.duyck@gmail.com,
intel-wired-lan@lists.osuosl.org, jeffrey.t.kirsher@intel.com,
netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [net-next PATCH 0/2] Follow-ups for GUEoIPv6 patches
Date: Fri, 20 May 2016 19:26:17 -0400 (EDT) [thread overview]
Message-ID: <20160520.192617.407123677086722342.davem@davemloft.net> (raw)
In-Reply-To: <20160518173605.2608.42484.stgit@localhost.localdomain>
From: Alexander Duyck <aduyck@mirantis.com>
Date: Wed, 18 May 2016 10:44:40 -0700
> This patch series is meant to be applied after:
> [PATCH v7 net-next 00/16] ipv6: Enable GUEoIPv6 and more fixes for v6 tunneling
>
> The first patch addresses an issue we already resolved in the GREv4 and is
> now present in GREv6 with the introduction of FOU/GUE for IPv6 based GRE
> tunnels.
>
> The second patch goes through and enables IPv6 tunnel offloads for the Intel
> NICs that already support the IPv4 based IP-in-IP tunnel offloads. I have
> only done a bit of touch testing but have seen ~20 Gb/s over an i40e
> interface using a v4-in-v6 tunnel, and I have verified IPv6 GRE is still
> passing traffic at around the same rate. I plan to do further testing but
> with these patches present it should enable a wider audience to be able to
> test the new features introduced in Tom's patchset with hardware offloads.
Series applied, thanks Alex.
prev parent reply other threads:[~2016-05-20 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 17:44 [net-next PATCH 0/2] Follow-ups for GUEoIPv6 patches Alexander Duyck
2016-05-18 17:44 ` [net-next PATCH 1/2] ip6_gre: Do not allow segmentation offloads GRE_CSUM is enabled with FOU/GUE Alexander Duyck
2016-05-18 17:44 ` [net-next PATCH 2/2] intel: Add support for IPv6 IP-in-IP offload Alexander Duyck
2016-05-18 21:27 ` [net-next PATCH 0/2] Follow-ups for GUEoIPv6 patches Jeff Kirsher
2016-05-18 23:19 ` Alexander Duyck
2016-05-18 23:31 ` Jeff Kirsher
2016-05-19 4:10 ` David Miller
2016-05-24 17:14 ` Jeff Kirsher
2016-05-24 17:46 ` Alex Duyck
2016-05-20 23:26 ` 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=20160520.192617.407123677086722342.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aduyck@mirantis.com \
--cc=alexander.duyck@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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).