summaryrefslogtreecommitdiffstats
path: root/net/tipc/node.c
diff options
context:
space:
mode:
authorJon Paul Maloy <jon.maloy@ericsson.com>2015-07-30 18:24:20 -0400
committerDavid S. Miller <davem@davemloft.net>2015-07-30 17:25:14 -0700
commit5045f7b9009f1455268b98cecbcc271663934c85 (patch)
treeb7398fdb0cca2fc7ac69fa8f699e451d3d895a1c /net/tipc/node.c
parent6e498158a827fd515b514842e9a06bdf0f75ab86 (diff)
downloadop-kernel-dev-5045f7b9009f1455268b98cecbcc271663934c85.zip
op-kernel-dev-5045f7b9009f1455268b98cecbcc271663934c85.tar.gz
tipc: move protocol message sending away from link FSM
The implementation of the link FSM currently takes decisions about and sends out link protocol messages. This is unnecessary, since such actions are not the result of any link state change, and are even decided based on non-FSM state information ("silent_intv_cnt"). We now move the sending of unicast link protocol messages to the function tipc_link_timeout(), and the initial broadcast synchronization message to tipc_node_link_up(). The latter is done because a link instance should not need to know whether it is the first or second link to a destination. Such information is now restricted to and handled by the link aggregation layer in node.c Tested-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/tipc/node.c')
-rw-r--r--net/tipc/node.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/net/tipc/node.c b/net/tipc/node.c
index b0372bb..9e20acf 100644
--- a/net/tipc/node.c
+++ b/net/tipc/node.c
@@ -335,6 +335,7 @@ static void tipc_node_link_up(struct tipc_node *n, int bearer_id,
*slot0 = bearer_id;
*slot1 = bearer_id;
nl->exec_mode = TIPC_LINK_OPEN;
+ tipc_link_build_bcast_sync_msg(nl, xmitq);
node_established_contact(n);
return;
}
OpenPOWER on IntegriCloud