Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keller, Jacob E <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 2/4] geneve: Add geneve udp port offload for ethernet devices
Date: Thu, 20 Aug 2015 20:32:13 +0000	[thread overview]
Message-ID: <1440102733.28850.4.camel@intel.com> (raw)
In-Reply-To: <1440096383-8915-2-git-send-email-anjali.singhai@intel.com>

On Thu, 2015-08-20 at 11:46 -0700, Anjali Singhai Jain wrote:
> Add ndo_ops to add/del UDP ports to a device that supports geneve
> offload.
> 
> v2:Added comments for new ndo_ops and minor format fix.
> 
> Signed-off-by: Kiran Patil <kiran.patil@intel.com>
> Signed-off-by: Anjali Singhai Jain <anjali.singhai@intel.com>
> ---
>  include/linux/netdevice.h | 20 +++++++++++++++++++-
>  net/ipv4/geneve_core.c    | 22 ++++++++++++++++++++++
>  2 files changed, 41 insertions(+), 1 deletion(-)
> 
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index f3bb290..d6f00c7 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -1016,6 +1016,19 @@ typedef u16 (*select_queue_fallback_t)(struct
> net_device *dev,
>   *	address family that vxlan is not listening to anymore. The
> operation
>   *	is protected by the vxlan_net->sock_lock.
>   *
> + * void (*ndo_add_geneve_port)(struct net_device *dev,
> + *			      sa_family_t sa_family, __be16 port);
> + *	Called by geneve to notiy a driver about the UDP port and
> socket
> + *	address family that geneve is listnening to. It is called
> only when
> + *	a new port starts listening. The operation is protected by
> the
> + *	geneve_net->sock_lock.
> + *
> + * void (*ndo_del_geneve_port)(struct net_device *dev,
> + *			      sa_family_t sa_family, __be16 port);
> + *	Called by geneve to notify the driver about a UDP port and
> socket
> + *	address family that geneve is not listening to anymore.
> The operation
> + *	is protected by the geneve_net->sock_lock.
> + *


Would it make more sense to generalize the ndo op for future protocol
extension instead of continuing to add separate tunnel offload
functions for each one?


ie: generalize ndo_add_vxlan_port into "ndo_add_tunnel_port"?

Maybe it's not worth it though..?

Regards,
Jake

  reply	other threads:[~2015-08-20 20:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 18:46 [Intel-wired-lan] [PATCH 1/4] i40e: Remove CONFIG_I40E_VXLAN Anjali Singhai Jain
2015-08-20 18:46 ` [Intel-wired-lan] [PATCH 2/4] geneve: Add geneve udp port offload for ethernet devices Anjali Singhai Jain
2015-08-20 20:32   ` Keller, Jacob E [this message]
2015-08-20 23:03     ` Singhai, Anjali
2015-08-22  0:13       ` Jesse Gross
2015-08-22  0:40         ` Singhai, Anjali
2015-08-20 20:37   ` Keller, Jacob E
2015-08-20 21:03     ` Singhai, Anjali
2015-08-20 18:46 ` [Intel-wired-lan] [PATCH 3/4] i40e: Generalize the UDP tunnel offload flow Anjali Singhai Jain
2015-08-21 22:54   ` Bowers, AndrewX
2015-08-20 18:46 ` [Intel-wired-lan] [PATCH 4/4] i40e: geneve tunnel offload support Anjali Singhai Jain
2015-08-21 22:55   ` Bowers, AndrewX
2015-08-22  0:38   ` Jesse Gross
2015-08-20 20:30 ` [Intel-wired-lan] [PATCH 1/4] i40e: Remove CONFIG_I40E_VXLAN Keller, Jacob E
2015-08-26 23:45 ` Bowers, AndrewX

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=1440102733.28850.4.camel@intel.com \
    --to=jacob.e.keller@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