linux.git/net/tipc/msg.h, branch v2.6.39

tipc: Eliminate obsolete routine for handling routed messages

2011-03-13T20:35:19+00:00

Eliminates a routine that is used in handling messages arriving from
another cluster or zone. Such messages can no longer be received by TIPC
now that multi-cluster and multi-zone network support has been eliminated.

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker

tipc: Eliminate remaining support for routing table messages

2011-03-13T20:35:19+00:00

Gets rid of all remaining code relating to ROUTE_DISTRIBUTOR messages.
These messages were only used in multi-cluster and multi-zone networks,
which TIPC no longer supports. (For safety, TIPC now treats such messages
the same way that it handles other unrecognized messages.)

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker

tipc: Eliminate unnecessary constant for neighbor discovery msg size

2011-03-13T20:35:18+00:00

Eliminates an unnecessary constant that defines the size of a LINK_CONFIG
message, and uses one of the existing standard message size symbols in
its place. (The defunct constant was located in the wrong place anyway,
since it was grouped with other constants that define message users instead
of message sizes.)

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker

tipc: make msg_set_redundant_link() consistent with other set ops

2011-03-13T20:35:17+00:00

All the other boolean like msg_set_X(m) operations don't
export both a msg_set_X(a) and a msg_clear_X(m), but instead
just have the single msg_set_X(m, val) variant.

Make the redundant_link one consistent by having the set take
a value, and delete the msg_clear_redundant_link() anomoly.
This is a cosmetic change and should not change behaviour.

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker

tipc: Eliminate timestamp from link protocol messages

2011-03-13T20:35:17+00:00

Removes support for the timestamp field of TIPC's link protocol messages.

This field was previously used to hold an OS-dependent timestamp value
that was used to assist in debugging early versions of TIPC. The field
has now been deemed unnecessary and has been removed from the latest TIPC
specification. This change has no impact on the operation of TIPC since
the field was set by TIPC, but never referenced.

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker

tipc: Remove unused message header field for requested number of links

2011-02-23T23:05:22+00:00

Eliminates support for the "number of requested links" field in a neighbor
discovery message. This field was never used and has been removed from
the TIPC 2.0 protocol specification.

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker

tipc: Remove support for per-connection message sequence numbering

2011-02-23T23:05:21+00:00

Eliminates TIPC's prototype support for message sequence numbering
on routable connections (i.e. connections requiring more than one hop).
This capability isn't currently used, and can be removed since TIPC
only supports systems in which all inter-node communication can be
achieved in a single hop.

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker

tipc: cleanup various cosmetic whitespace issues

2011-01-01T21:57:56+00:00

Cleans up TIPC's source code to eliminate deviations from generally
accepted coding conventions relating to leading/trailing white space
and white space around commas, braces, cases, and sizeof.

These changes are purely cosmetic and do not alter the operation of TIPC
in any way.

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker 
Signed-off-by: David S. Miller

tipc: Remove prototype code for supporting inter-cluster routing

2011-01-01T21:57:48+00:00

Eliminates routines and data structures that were intended to allow
TIPC to route messages to other clusters. Currently, TIPC supports only
networks consisting of a single cluster within a single zone, so this
code is unnecessary.

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker 
Signed-off-by: David S. Miller

tipc: Remove prototype code for supporting slave nodes

2011-01-01T21:57:48+00:00

Simplifies routines and data structures that were intended to allow
TIPC to support slave nodes (i.e. nodes that did not have links to
all of the other nodes in its cluster, forcing TIPC to route messages
that it could not deliver directly through a non-slave node).

Currently, TIPC supports only networks containing non-slave nodes,
so this code is unnecessary.

Note: The latest edition of the TIPC 2.0 Specification has eliminated
the concept of slave nodes entirely.

Signed-off-by: Allan Stephens 
Signed-off-by: Paul Gortmaker 
Signed-off-by: David S. Miller