Re: [PATCH net-next v2] net: link_watch: mark bonding link events urgent

2018-01-23 Thread David Miller
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: multichas

Re: [PATCH net-next v2] net: link_watch: mark bonding link events urgent

2018-01-23 Thread Nikolay Aleksandrov
On 22/01/18 18:07, Roopa Prabhu wrote: > 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 implementati

Re: [PATCH net-next v2] net: link_watch: mark bonding link events urgent

2018-01-22 Thread Jiri Pirko
Mon, Jan 22, 2018 at 05:07:19PM CET, ro...@cumulusnetworks.com wrote: >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: mult

[PATCH net-next v2] net: link_watch: mark bonding link events urgent

2018-01-22 Thread Roopa Prabhu
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 alrea