diff options
author | Jon Paul Maloy <jon.maloy@ericsson.com> | 2017-08-21 17:59:30 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-08-21 13:37:45 -0700 |
commit | 40501f90ed5d992176ba504910d512d9dd1b2668 (patch) | |
tree | 2a5a284828650f3d7da6b84d81b12d394d76c085 /net/rxrpc/output.c | |
parent | e65a4955b0bb70ab66e2fbfd5509747fe51d8bf9 (diff) |
tipc: don't reset stale broadcast send link
When the broadcast send link after 100 attempts has failed to
transfer a packet to all peers, we consider it stale, and reset
it. Thereafter it needs to re-synchronize with the peers, something
currently done by just resetting and re-establishing all links to
all peers. This has turned out to be overkill, with potentially
unwanted consequences for the remaining cluster.
A closer analysis reveals that this can be done much simpler. When
this kind of failure happens, for reasons that may lie outside the
TIPC protocol, it is typically only one peer which is failing to
receive and acknowledge packets. It is hence sufficient to identify
and reset the links only to that peer to resolve the situation, without
having to reset the broadcast link at all. This solution entails a much
lower risk of negative consequences for the own node as well as for
the overall cluster.
We implement this change in this commit.
Reviewed-by: Parthasarathy Bhuvaragan <parthasarathy.bhuvaragan@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/rxrpc/output.c')
0 files changed, 0 insertions, 0 deletions