diff options
author | Jon Paul Maloy <jon.maloy@ericsson.com> | 2015-10-22 08:51:47 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2015-10-24 06:56:46 -0700 |
commit | c49a0a84391bcc313b3dc2a9ceee6de684e07655 (patch) | |
tree | 5f4c6686b23b073ff210628f666f1a73de8c6cd2 /drivers/edac/x38_edac.c | |
parent | c72fa872a23f03b2b9c17e88f3b0a8070924e5f1 (diff) | |
download | blackbird-op-linux-c49a0a84391bcc313b3dc2a9ceee6de684e07655.tar.gz blackbird-op-linux-c49a0a84391bcc313b3dc2a9ceee6de684e07655.zip |
tipc: ensure binding table initial distribution is sent via first link
Correct synchronization of the broadcast link at first contact between
two nodes is dependent on the assumption that the binding table "bulk"
update passes via the same link as the initial broadcast syncronization
message, i.e., via the first link that is established.
This is not guaranteed in the current implementation. If two link
come up very close to each other in time, the "bulk" may quite well
pass via the second link, and hence void the guarantee of a correct
initial synchronization before the broadcast link is opened.
This commit makes two small changes to strengthen this guarantee.
1) We let the second established link occupy slot 1 of the
"active_links" array, while the first link will retain slot 0.
(This is in reality a cosmetic change, we could just as well keep
the current, opposite order)
2) We let the name distributor always use link selector/slot 0 when
it sends it binding table updates.
The extra traffic bias on the first link caused by this change should
be negligible, since binding table updates constitutes a very small
fraction of the total traffic.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Reviewed-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/edac/x38_edac.c')
0 files changed, 0 insertions, 0 deletions