Lines Matching refs:outbound
205 In this discussion, the "outbound side" is the view of the cluster state
215 on the outbound side:
247 Transitions -----> can only be made by the outbound CPU, and
252 further transition possible on the outbound side (i.e., the
253 outbound CPU has put the cluster into the CLUSTER_DOWN state).
264 The parallelism of the inbound and outbound CPUs is observed by
283 can occur; either the inbound or the outbound side.
338 Next state: CLUSTER_GOING_DOWN/INBOUND_NOT_COMING_UP (outbound)
345 An outbound CPU is tearing the cluster down. The selected CPU
353 To avoid wasteful unnecessary teardown operations, the outbound
361 CLUSTER_DOWN/INBOUND_NOT_COMING_UP (outbound)
382 If the outbound CPU observes this state, it has two choices:
398 CLUSTER_UP/INBOUND_COMING_UP (outbound)
403 CLUSTER_DOWN/INBOUND_COMING_UP (outbound)
411 The CPU which performs cluster tear-down operations on the outbound side