A TIPC 1.7 link endpoint does not always processing incoming messages in sequential order if its bearer utilizes a driver with multiple receiving threads. This can be illustrated by the following sequence of events, involving a node with multi-core CPUs A and B:
cpu A
1) invokes tipc_recv_msg() with packet N
2) performs read_lock_bh(&tipc_net_lock) [this ensures TIPC's view of the network...
Laser [gotolaser@gmail.com] has determined that VxWorks TIPC 1.7 does not support Ethernet VLAN interfaces, unlike Linux TIPC 1.7.
Laser has created a prototype patch for TIPC 1.7.6 which seems to provide this functionality (at least on VxWorks 6.3). Al has provided feedback (see below) that describes how the patch might be improved.
> - I'm not an expert in how VLAN code works in VxWorks,
