tipc: optimize link synching mechanism
This commit along with the next one are to resolve the issues with the link changeover mechanism. See that commit for details. Basically, for the link synching, from now on, we will send only one single ("dummy") SYNCH message to peer. The SYNCH message does not contain any data, just a header conveying the synch point to the peer. A new node capability flag ("TIPC_TUNNEL_ENHANCED") is introduced for backward compatible! Acked-by: Ying Xue <ying.xue@windriver.com> Acked-by: Jon Maloy <jon.maloy@ericsson.com> Suggested-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: Tuong Lien <tuong.t.lien@dektech.com.au> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:

committed by
David S. Miller

parent
37f7c66f45
commit
4929a932be
@@ -53,7 +53,8 @@ enum {
|
||||
TIPC_NODE_ID128 = (1 << 5),
|
||||
TIPC_LINK_PROTO_SEQNO = (1 << 6),
|
||||
TIPC_MCAST_RBCTL = (1 << 7),
|
||||
TIPC_GAP_ACK_BLOCK = (1 << 8)
|
||||
TIPC_GAP_ACK_BLOCK = (1 << 8),
|
||||
TIPC_TUNNEL_ENHANCED = (1 << 9)
|
||||
};
|
||||
|
||||
#define TIPC_NODE_CAPABILITIES (TIPC_SYN_BIT | \
|
||||
@@ -64,7 +65,8 @@ enum {
|
||||
TIPC_NODE_ID128 | \
|
||||
TIPC_LINK_PROTO_SEQNO | \
|
||||
TIPC_MCAST_RBCTL | \
|
||||
TIPC_GAP_ACK_BLOCK)
|
||||
TIPC_GAP_ACK_BLOCK | \
|
||||
TIPC_TUNNEL_ENHANCED)
|
||||
#define INVALID_BEARER_ID -1
|
||||
|
||||
void tipc_node_stop(struct net *net);
|
||||
|
Reference in New Issue
Block a user