netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: arp_notify: allow drivers to explicitly request a notification event.
Date: Wed, 11 Aug 2010 12:39:59 -0700	[thread overview]
Message-ID: <20100811193959.GA9470@kroah.com> (raw)
In-Reply-To: <20100811193925.GA9452@kroah.com>

On Wed, Aug 11, 2010 at 12:39:25PM -0700, Greg KH wrote:
> Wait, Ian, are you sure this patch is correct?  Look below in
> notifier.h:
> 
> On Wed, May 26, 2010 at 12:09:42AM +0000, Ian Campbell wrote:
> > From: Ian Campbell <Ian.Campbell@citrix.com>
> > 
> > commit 06c4648d46d1b757d6b9591a86810be79818b60c upstream.
> > 
> > Currently such notifications are only generated when the device comes up or the
> > address changes. However one use case for these notifications is to enable
> > faster network recovery after a virtual machine migration (by causing switches
> > to relearn their MAC tables). A migration appears to the network stack as a
> > temporary loss of carrier and therefore does not trigger either of the current
> > conditions. Rather than adding carrier up as a trigger (which can cause issues
> > when interfaces a flapping) simply add an interface which the driver can use
> > to explicitly trigger the notification.
> > 
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> > Cc: Stephen Hemminger <shemminger@linux-foundation.org>
> > Cc: Jeremy Fitzhardinge <jeremy@goop.org>
> > Cc: David S. Miller <davem@davemloft.net>
> > Cc: netdev@vger.kernel.org
> > Signed-off-by: David S. Miller <davem@davemloft.net>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> > 
> > --- a/include/linux/netdevice.h
> > +++ b/include/linux/netdevice.h
> > @@ -1772,6 +1772,8 @@ extern void netif_carrier_on(struct net_device *dev);
> >  
> >  extern void netif_carrier_off(struct net_device *dev);
> >  
> > +extern void netif_notify_peers(struct net_device *dev);
> > +
> >  /**
> >   *	netif_dormant_on - mark device as dormant.
> >   *	@dev: network device
> > diff --git a/include/linux/notifier.h b/include/linux/notifier.h
> > index 540703b..22c2abb 100644
> > --- a/include/linux/notifier.h
> > +++ b/include/linux/notifier.h
> > @@ -210,6 +210,7 @@ static inline int notifier_to_errno(int ret)
> >  #define NETDEV_POST_INIT	0x0010
> >  #define NETDEV_UNREGISTER_BATCH 0x0011
> >  #define NETDEV_BONDING_DESLAVE  0x0012
> > +#define NETDEV_NOTIFY_PEERS	0x0012
> 
> Are you sure that you can duplicate this value?

Oh nevermind, David already fixed this up with commit
38117d1495e587fbb10d6e55733139a27893cef5

I'll go queue that up for -stable as well :)

thanks,

greg k-h

  reply	other threads:[~2010-08-11 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 19:39 arp_notify: allow drivers to explicitly request a notification event Greg KH
2010-08-11 19:39 ` Greg KH [this message]
2010-08-11 20:16   ` Ian Campbell

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=20100811193959.GA9470@kroah.com \
    --to=greg@kroah.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=davem@davemloft.net \
    --cc=jeremy@goop.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).