Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v6 1/6] net: Generalize udp based tunnel offload
Date: Tue, 24 Nov 2015 13:03:55 -0800	[thread overview]
Message-ID: <1448399035.3154.7.camel@intel.com> (raw)
In-Reply-To: <1448262224-71480-2-git-send-email-anjali.singhai@intel.com>

On Sun, 2015-11-22 at 23:03 -0800, Anjali Singhai Jain wrote:
> Replace add/del ndo ops for vxlan_port with tunnel_port so that all
> UDP
> based tunnels can use the same ndo op. Add a parameter to pass tunnel
> type to the ndo_op.
> 
> Change all drivers to use the generalized udp tunnel offload
> 
> Patch was compile tested with x86_64_defconfig.
> 
> Signed-off-by: Kiran Patil <kiran.patil@intel.com>
> Signed-off-by: Anjali Singhai Jain <anjali.singhai@intel.com>
> ---
> ?drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c | 15 ++++++---
> ?drivers/net/ethernet/broadcom/bnxt/bnxt.c??????? | 13 +++++---
> ?drivers/net/ethernet/emulex/benet/be_main.c????? | 14 +++++---
> ?drivers/net/ethernet/intel/fm10k/fm10k_netdev.c? | 27 ++++++++++++
> ----
> ?drivers/net/ethernet/intel/i40e/i40e_main.c????? | 41
> +++++++++++++++++-------
> ?drivers/net/ethernet/intel/ixgbe/ixgbe_main.c??? | 17 +++++++---
> ?drivers/net/ethernet/mellanox/mlx4/en_netdev.c?? | 21 ++++++++----
> ?drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c | 17 +++++++---
> ?drivers/net/vxlan.c????????????????????????????? | 23 +++++++------
> ?include/linux/netdevice.h??????????????????????? | 34 ++++++++++--
> --------
> ?include/net/udp_tunnel.h???????????????????????? |? 6 ++++
> ?11 files changed, 157 insertions(+), 71 deletions(-)

This patch breaks the Broadcom drivers, they don't even compile after
this patch.

Dropping this series until the compile issues are resolved.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20151124/ec8c99ad/attachment.asc>

  reply	other threads:[~2015-11-24 21:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <anjali.singhai@intel.com>
2015-11-23  7:03 ` [Intel-wired-lan] [PATCH 0/6] Generalize udp based tunnels and add geneve offload Anjali Singhai Jain
2015-11-23  7:03   ` [Intel-wired-lan] [PATCH v6 1/6] net: Generalize udp based tunnel offload Anjali Singhai Jain
2015-11-24 21:03     ` Jeff Kirsher [this message]
2015-11-24 22:31       ` Singhai, Anjali
2015-11-23  7:03   ` [Intel-wired-lan] [PATCH v6 2/6] net: Add a generic udp_offload_get_port function Anjali Singhai Jain
2015-11-23  7:03   ` [Intel-wired-lan] [PATCH v6 3/6] i40e: Generalize the flow for udp based tunnels Anjali Singhai Jain
2015-11-23  7:03   ` [Intel-wired-lan] [PATCH v6 4/6] i40e: Remove CONFIG_I40E_VXLAN Anjali Singhai Jain
2015-11-23  7:03   ` [Intel-wired-lan] [PATCH v6 5/6] net: Refactor udp_offload and add Geneve port offload support Anjali Singhai Jain
2015-11-23  7:03   ` [Intel-wired-lan] [PATCH v6 6/6] i40e:Add geneve tunnel " Anjali Singhai Jain
2015-11-23 18:11   ` [Intel-wired-lan] [PATCH 0/6] Generalize udp based tunnels and add geneve offload Jesse Gross

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=1448399035.3154.7.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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