From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next v2] net: link_watch: mark bonding link events urgent Date: Tue, 23 Jan 2018 19:43:54 -0500 (EST) Message-ID: <20180123.194354.1714709617379610153.davem@davemloft.net> References: <1516637239-47607-1-git-send-email-roopa@cumulusnetworks.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, nikolay@cumulusnetworks.com, dsa@cumulusnetworks.com, jiri@resnulli.us To: roopa@cumulusnetworks.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:34620 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932238AbeAXAn5 (ORCPT ); Tue, 23 Jan 2018 19:43:57 -0500 In-Reply-To: <1516637239-47607-1-git-send-email-roopa@cumulusnetworks.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Roopa Prabhu Date: Mon, 22 Jan 2018 08:07:19 -0800 > From: Roopa Prabhu > > 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 > --- > v2: use netif_is_lag_* api's as suggested by jiri Applied, thanks Roopa.