From: Joseph Gasparakis <joseph.gasparakis@intel.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
davem@davemloft.net,
Joseph Gasparakis <joseph.gasparakis@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com,
John Fastabend <john.r.fastabend@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [net-next v2 1/2] vxlan: Notify drivers for listening UDP port changes
Date: Thu, 29 Aug 2013 12:55:59 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.03.1308291254290.25550@intel.com> (raw)
In-Reply-To: <1377801778.5372.8.camel@bwh-desktop.uk.level5networks.com>
On Thu, 29 Aug 2013, Ben Hutchings wrote:
> On Thu, 2013-08-29 at 05:54 -0700, Jeff Kirsher wrote:
> > From: Joseph Gasparakis <joseph.gasparakis@intel.com>
> >
> > This patch adds two more ndo ops: ndo_add_rx_vxlan_port() and
> > ndo_del_rx_vxlan_port().
> [...]
> > --- a/include/linux/netdevice.h
> > +++ b/include/linux/netdevice.h
> > @@ -948,6 +948,18 @@ struct netdev_phys_port_id {
> > * Called to get ID of physical port of this device. If driver does
> > * not implement this, it is assumed that the hw is not able to have
> > * multiple net devices on single physical port.
> > + *
> > + * int (*ndo_add_vxlan_port)(struct net_device *dev,
> > + * __u16 port);
> > + * Called by vxlan to notiy a driver about the UDP port that vxlan
> > + * is listnening to. It is called only when a new port starts listening.
> > + * The operation is protected by the vxlan_net->sock_lock.
> > + *
> > + * int (*ndo_del_vxlan_port)(struct net_device *dev,
> > + * __u16 port);
> > + * Called by vxlan to notify the driver about a UDP port of vxlan
> > + * that is not listening anymore. The operation is protected by
> > + * the vxlan_net->sock_lock.
> > */
> > struct net_device_ops {
> > int (*ndo_init)(struct net_device *dev);
> > @@ -1078,6 +1090,10 @@ struct net_device_ops {
> > bool new_carrier);
> > int (*ndo_get_phys_port_id)(struct net_device *dev,
> > struct netdev_phys_port_id *ppid);
> > + int (*ndo_add_vxlan_port)(struct net_device *dev,
> > + __u16 port);
> > + int (*ndo_del_vxlan_port)(struct net_device *dev,
> > + __u16 port);
> > };
> [...]
>
> I notice these are defined to return int, but the callers don't check
> the return value. Should they return void or do the callers need some
> error handling?
>
> Ben.
>
>
You are right Ben, these should be defined to return void. Will fix that
asap.
Joseph
prev parent reply other threads:[~2013-08-29 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 12:54 [net-next v2 1/2] vxlan: Notify drivers for listening UDP port changes Jeff Kirsher
2013-08-29 12:54 ` [net-next RFC v2 2/2] ixgbe: Get and display the notifications from changes of the Rx vxlan UDP port Jeff Kirsher
2013-08-29 14:19 ` [net-next v2 1/2] vxlan: Notify drivers for listening UDP port changes Jiri Pirko
2013-08-29 16:49 ` Joseph Gasparakis
2013-08-29 18:42 ` Ben Hutchings
2013-08-29 19:55 ` Joseph Gasparakis [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=alpine.LFD.2.03.1308291254290.25550@intel.com \
--to=joseph.gasparakis@intel.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).