[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180123.194354.1714709617379610153.davem@davemloft.net>
Date: Tue, 23 Jan 2018 19:43:54 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: roopa@...ulusnetworks.com
Cc: netdev@...r.kernel.org, nikolay@...ulusnetworks.com,
dsa@...ulusnetworks.com, jiri@...nulli.us
Subject: Re: [PATCH net-next v2] net: link_watch: mark bonding link events
urgent
From: Roopa Prabhu <roopa@...ulusnetworks.com>
Date: Mon, 22 Jan 2018 08:07:19 -0800
> From: Roopa Prabhu <roopa@...ulusnetworks.com>
>
> It takes 1sec for bond link down notification to hit user-space
> when all slaves of the bond go down. 1sec is too long for
> protocol daemons in user-space relying on bond notification
> to recover (eg: multichassis lag implementations in user-space).
> Since the link event code already marks team device port link events
> as urgent, this patch moves the code to cover all lag ports and master.
>
> Signed-off-by: Roopa Prabhu <roopa@...ulusnetworks.com>
> ---
> v2: use netif_is_lag_* api's as suggested by jiri
Applied, thanks Roopa.
Powered by blists - more mailing lists