[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <56AB0F53.5080600@gmail.com>
Date: Fri, 29 Jan 2016 15:05:55 +0800
From: zhuyj <zyjzyj2000@...il.com>
To: Jay Vosburgh <jay.vosburgh@...onical.com>
Cc: mkubecek@...e.cz, vfalico@...il.com, gospo@...ulusnetworks.com,
netdev@...r.kernel.org, boris.shteinbock@...driver.com,
emil.s.tantilov@...el.com, zhuyj <zyjzyj2000@...il.com>
Subject: Re: [PATCH 1/1] bonding: Use notifiers for slave link state detection
Thanks a lot.
Maybe this patch is to miimon and notifier. Maybe it is not appropriate to arp monitor.
So the following patch will avoid arp monitor.
Thanks a lot.
Zhu Yanjun
+ /* Because of link flap from the slave interface, it is possilbe that
+ * the notifiler is NETDEV_UP while the actual link state is down. If
+ * so, it is not necessary to contiune.
+ */
+ if (!bond->params.arp_interval) {
+ switch (event) {
+ case NETDEV_UP:
+ if (!link_state)
+ return 0;
+ break;
+
+ case NETDEV_DOWN:
+ if (link_state)
+ return 0;
+ break;
+ }
+ }
On 01/26/2016 02:00 PM, Jay Vosburgh wrote:
> + /* Because of link flap from the slave interface, it is possilbe that
> + * the notifiler is NETDEV_UP while the actual link state is down. If
> + * so, it is not necessary to contiune.
> + */
> + switch (event) {
> + case NETDEV_UP:
> + if (!link_state)
> + return 0;
> + break;
> +
> + case NETDEV_DOWN:
> + if (link_state)
> + return 0;
> + break;
> + }
> +
Powered by blists - more mailing lists