When we send broadcasts in clusters of more 70-80 nodes, we sometimes
see the broadcast link resetting because of an excessive number of
retransmissions. This is caused by a combination of two factors:
1) A 'NACK crunch", where loss of broadcast packets is discovered
and NACK'ed by several node
When we send broadcasts in clusters of more 70-80 nodes, we sometimes
see the broadcast link resetting because of an excessive number of
retransmissions. This is caused by a combination of two factors:
1) A 'NACK crunch", where loss of broadcast packets is discovered
and NACK'ed by several node
-Original Message-
From: Jon Maloy [mailto:jon.ma...@ericsson.com]
Sent: Wednesday, August 17, 2016 2:09 AM
To: tipc-discussion@lists.sourceforge.net;
parthasarathy.bhuvara...@ericsson.com; Xue, Ying; richard.a...@ericsson.com;
jon.ma...@ericsson.com
Cc: ma...@donjonn.com; gbala...@gmail
> -Original Message-
> From: Xue, Ying [mailto:ying@windriver.com]
> Sent: Tuesday, 23 August, 2016 05:48
> To: Jon Maloy ; tipc-discussion@lists.sourceforge.net;
> Parthasarathy Bhuvaragan ; Richard
> Alpe
> Cc: ma...@donjonn.com; gbala...@gmail.com
> Subject: RE: [PATCH net-next 1/
Hi Jon,
Thank you for the clear explanation below, and now I am sure that the patch is
no problem with me.
Regards,
Ying
-Original Message-
From: Jon Maloy [mailto:jon.ma...@ericsson.com]
Sent: Tuesday, August 23, 2016 9:55 PM
To: Xue, Ying; tipc-discussion@lists.sourceforge.net; Parth
