/usr/src/linux/Documentation/networking/bonding.txt您最喜欢的发行版的linux源代码包中的文档文件中对这些要点中的大多数进行了详尽的描述。对于大多数模式，故障转移的速度由“ miimon”参数控制，但不应设置得太低。正常值在1秒以内。
这是我完成的最好的部分：
balance-rr or 0
Round-robin policy: Transmit packets in sequential
order from the first available slave through the
last. This mode provides load balancing and fault
tolerance.
active-backup or 1
Active-backup policy: Only one slave in the bond is
active. A different slave becomes active if, and only
if, the active slave fails. The bond's MAC address is
externally visible on only one port (network adapter)
to avoid confusing the switch.
This mode provides fault tolerance. The "primary"
option affects the behavior of this mode.
balance-xor or 2
XOR policy: Transmit based on the selected transmit
hash policy. The default policy is a simple [(source
MAC address XOR'd with destination MAC address) modulo
slave count]. Alternate transmit policies may be
selected via the xmit_hash_policy option.
This mode provides load balancing and fault tolerance.
broadcast or 3
Broadcast policy: transmits everything on all slave
interfaces. This mode provides fault tolerance.
802.3ad or 4
IEEE 802.3ad Dynamic link aggregation. Creates
aggregation groups that share the same speed and
duplex settings. Utilizes all slaves in the active
aggregator according to the 802.3ad specification.
Slave selection for outgoing traffic is done according
to the transmit hash policy, which may be changed from
the default simple XOR policy via the xmit_hash_policy
option. Note that not all transmit policies may be 802.3ad
compliant, particularly inregards to the packet mis-ordering
requirements of section 43.2.4 of the 802.3ad standard.
Differing peer implementations will have varying tolerances for
noncompliance.
Note: Most switches will require some type of configuration
to enable 802.3ad mode.
balance-tlb or 5
Adaptive transmit load balancing: channel bonding that
does not require any special switch support. The
outgoing traffic is distributed according to the
current load (computed relative to the speed) on each
slave. Incoming traffic is received by the current
slave. If the receiving slave fails, another slave
takes over the MAC address of the failed receiving
slave.
balance-alb or 6
Adaptive load balancing: includes balance-tlb plus
receive load balancing (rlb) for IPV4 traffic, and
does not require any special switch support.
When a link is reconnected or a new slave joins the
bond the receive traffic is redistributed among all
active slaves in the bond by initiating ARP Replies
with the selected MAC address to each of the
clients. The updelay parameter must
be set to a value equal or greater than the switch's
forwarding delay so that the ARP Replies sent to the
peers will not be blocked by the switch.
balance-rr，active-backup，balance-tlb和balance-alb不需要开关支持。
balance-rr以碎片为代价提高了性能，在某些协议（CIFS）和两个以上的接口上表现不佳。
balance-alb和balance-tlb可能不适用于所有交换机；通常存在一些arp问题（例如，某些机器可能无法彼此连接）。您可能需要调整各种设置（miimon，updelay）以获得稳定的网络。
balance-xor可能需要交换机配置，也可能不需要。您需要在HP和Cisco交换机上设置接口组（不是 LACP），但是显然在D-Link，Netgear和Fujitsu交换机上没有必要。
802.3ad在交换机端绝对需要一个LACP组。总体而言，这是增强性能的最佳支持选项。
注意：无论您做什么，一个网络连接始终会通过一条物理链接，并且仅通过一条物理链接。因此，在聚合GigE接口时，即使每台计算机具有4个聚合的GigE接口（无论使用何种绑定模式），从计算机A到计算机B的文件传输速度也不能达到1 Gb / s。