Netdev List
 help / color / mirror / Atom feed
From: Alexander Duyck <aduyck@mirantis.com>
To: eugenia@mellanox.com, bruce.w.allan@intel.com,
	saeedm@mellanox.com, netdev@vger.kernel.org,
	intel-wired-lan@lists.osuosl.org, ariel.elior@qlogic.com,
	mchan@broadcom.com
Subject: [RFC PATCH 0/5] Add GSO Partial support for devices with existing tunnel offloads
Date: Tue, 19 Apr 2016 15:05:50 -0400	[thread overview]
Message-ID: <20160419185949.11723.50506.stgit@ahduyck-xeon-server> (raw)

This patch set is meant to extend tunnel offload support for devices that
already support UDP or GRE tunnels to include support for those type of
tunnels with an outer checksum.  To do this I am enabling GSO partial
support for these types of tunnels which should work assuming the devices
supported by these drivers are either overwriting or ignoring checksum and
length fields contained in the IPv4/v6 and ignoring the checksum contained
in the outer L4 tunnel headers.

I don't have any of the hardware that uses the drivers that these patches
are applied do.  That was one of the motivations for submitting them as RFC.
My hope is that somebody out there with this hardware is willing to pull in
the patch and test it out in order to determine if this approach actually
works for these devices.

---

Alexander Duyck (5):
      mlx4: Add support for UDP tunnel segmentation with outer checksum offload
      mlx5: Add support for UDP tunnel segmentation with outer checksum offload
      bnx2x: Add support for segmentation of tunnels with outer checksums
      bnxt: Add support for segmentation of tunnels with outer checksums
      fm10k: Add support for UDP tunnel segmentation with outer checksum offload


 drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c  |   13 ++++++++++---
 drivers/net/ethernet/broadcom/bnxt/bnxt.c         |    9 +++++++--
 drivers/net/ethernet/intel/fm10k/fm10k_netdev.c   |   14 ++++++++++----
 drivers/net/ethernet/mellanox/mlx4/en_netdev.c    |   17 +++++++++++++----
 drivers/net/ethernet/mellanox/mlx5/core/en_main.c |    7 ++++++-
 5 files changed, 46 insertions(+), 14 deletions(-)

             reply	other threads:[~2016-04-19 19:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 19:05 Alexander Duyck [this message]
2016-04-19 19:05 ` [RFC PATCH 1/5] mlx4: Add support for UDP tunnel segmentation with outer checksum offload Alexander Duyck
2016-04-19 19:06 ` [RFC PATCH 2/5] mlx5: " Alexander Duyck
2016-04-20 17:40   ` Saeed Mahameed
2016-04-20 18:06     ` Alexander Duyck
2016-04-28 21:43       ` Matthew Finlay
2016-04-28 22:04         ` Alexander Duyck
2016-04-29  1:18           ` Matthew Finlay
2016-04-29  1:59             ` Alexander Duyck
2016-04-29 19:27               ` Saeed Mahameed
2016-04-29 19:36                 ` Alexander Duyck
2016-04-19 19:06 ` [RFC PATCH 3/5] bnx2x: Add support for segmentation of tunnels with outer checksums Alexander Duyck
2016-08-24 12:33   ` Yuval Mintz
2016-08-24 15:39     ` Alexander Duyck
2016-08-25  5:06       ` Yuval Mintz
2016-08-25 18:26         ` Alexander Duyck
2016-08-31 11:31           ` Yuval Mintz
2016-08-31 16:13             ` Alexander Duyck
2016-04-19 19:06 ` [RFC PATCH 4/5] bnxt: " Alexander Duyck
2016-04-27  5:55   ` Michael Chan
2016-04-27 15:21     ` Alexander Duyck
2016-04-28  4:32       ` Michael Chan
2016-04-29 21:17         ` Alexander Duyck
2016-04-29 21:29           ` Michael Chan
2016-04-29 21:31             ` Alexander Duyck
2016-04-29 23:29               ` Michael Chan
2016-04-29 23:39                 ` Alexander Duyck
2016-04-19 19:06 ` [RFC PATCH 5/5] fm10k: Add support for UDP tunnel segmentation with outer checksum offload Alexander Duyck

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=20160419185949.11723.50506.stgit@ahduyck-xeon-server \
    --to=aduyck@mirantis.com \
    --cc=ariel.elior@qlogic.com \
    --cc=bruce.w.allan@intel.com \
    --cc=eugenia@mellanox.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.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