[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100523.233722.232536798.davem@davemloft.net>
Date: Sun, 23 May 2010 23:37:22 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: Ian.Campbell@...rix.com
Cc: netdev@...r.kernel.org, shemminger@...ux-foundation.org,
jeremy.fitzhardinge@...rix.com, stable@...nel.org
Subject: Re: [PATCH 0/2] fixes to arp_notify for virtual machine migration
use case
From: Ian Campbell <Ian.Campbell@...rix.com>
Date: Wed, 12 May 2010 14:39:14 +0100
> Ian Campbell (2):
> arp_notify: generate broadcast ARP reply not request.
> arp_notify: generate arp_notify event on NETDEV_CHANGE too
I don't agree with these changes.
For the first one, I think the documentation is just wrong and the
code is what expresses the intent. The idea is not to spam the
world with a broadcast, only interested parties.
Patch #2 I have major issues with, carriers flapping occaisionally is
very common. I have several interfaces which do this even on lightly
loaded networks. Iff we decide to do something like this (big "if")
it would need to be rate limited so that it doesn't trigger due to
normal flapping.
If you want your VM networking devices to trigger this event maybe
the best thing to do is to create a special notification which
allows us to prevent from doing this ARP notify for spurious physical
network device carrier flaps.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists