Mon, Jan 22, 2018 at 04:14:17PM CET, ro...@cumulusnetworks.com wrote:
>On Mon, Jan 22, 2018 at 12:13 AM, Jiri Pirko wrote:
>> Mon, Jan 22, 2018 at 07:07:53AM CET, ro...@cumulusnetworks.com wrote:
>>>From: Roopa Prabhu
>>>
>>>It takes 1sec for bond link down notification to hit user-space
>>>when
On Mon, Jan 22, 2018 at 12:13 AM, Jiri Pirko wrote:
> Mon, Jan 22, 2018 at 07:07:53AM 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 u
Mon, Jan 22, 2018 at 07:07:53AM 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 link notification
>to failover/rec
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 link notification
to failover/recover (eg: multichassis lag implementations in user-space).
Since the link ev
