lk/linux-kernel-test
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

bonding: update bonding.txt for Layer2 hash factors

Browse Source 
Document the Layer 2 hash factors with packet type ID field.

CC: Jay Vosburgh <j.vosburgh@gmail.com>
CC: Veaceslav Falico <vfalico@gmail.com>
CC: Andy Gospodarek <andy@greyhouse.net>
CC: David S. Miller <davem@davemloft.net>
CC: Pan Jiafei <Jiafei.Pan@freescale.com>

Signed-off-by: Jianhua Xie <jianhua.xie@freescale.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
Jianhua Xie
2014-07-17 14:16:26 +08:00
committed by David S. Miller
parent ce04d63502
commit 92abf75033
1 changed files with 16 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
Documentation/networking/bonding.txt
View File

@@ -542,10 +542,10 @@ mode
XOR policy: Transmit based on the selected transmit XOR policy: Transmit based on the selected transmit
hash policy. The default policy is a simple [(source hash policy. The default policy is a simple [(source
MAC address XOR'd with destination MAC address) modulo MAC address XOR'd with destination MAC address XOR
slave count]. Alternate transmit policies may be packet type ID) modulo slave count]. Alternate transmit
selected via the xmit_hash_policy option, described policies may be selected via the xmit_hash_policy option,
below. described below.
This mode provides load balancing and fault tolerance. This mode provides load balancing and fault tolerance.
@@ -801,10 +801,11 @@ xmit_hash_policy
layer2 layer2
Uses XOR of hardware MAC addresses to generate the Uses XOR of hardware MAC addresses and packet type ID
hash. The formula is field to generate the hash. The formula is
(source MAC XOR destination MAC) modulo slave count hash = source MAC XOR destination MAC XOR packet type ID
slave number = hash modulo slave count
This algorithm will place all traffic to a particular This algorithm will place all traffic to a particular
network peer on the same slave. network peer on the same slave.
@@ -819,7 +820,7 @@ xmit_hash_policy
Uses XOR of hardware MAC addresses and IP addresses to Uses XOR of hardware MAC addresses and IP addresses to
generate the hash. The formula is generate the hash. The formula is
hash = source MAC XOR destination MAC hash = source MAC XOR destination MAC XOR packet type ID
hash = hash XOR source IP XOR destination IP hash = hash XOR source IP XOR destination IP
hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 16)
hash = hash XOR (hash RSHIFT 8) hash = hash XOR (hash RSHIFT 8)
@@ -2301,13 +2302,13 @@ broadcast: Like active-backup, there is not much advantage to this
bandwidth. bandwidth.
Additionally, the linux bonding 802.3ad implementation Additionally, the linux bonding 802.3ad implementation
distributes traffic by peer (using an XOR of MAC addresses), distributes traffic by peer (using an XOR of MAC addresses
so in a "gatewayed" configuration, all outgoing traffic will and packet type ID), so in a "gatewayed" configuration, all
generally use the same device. Incoming traffic may also end outgoing traffic will generally use the same device. Incoming
up on a single device, but that is dependent upon the traffic may also end up on a single device, but that is
balancing policy of the peer's 8023.ad implementation. In a dependent upon the balancing policy of the peer's 8023.ad
"local" configuration, traffic will be distributed across the implementation. In a "local" configuration, traffic will be
devices in the bond. distributed across the devices in the bond.
Finally, the 802.3ad mode mandates the use of the MII monitor, Finally, the 802.3ad mode mandates the use of the MII monitor,
therefore, the ARP monitor is not available in this mode. therefore, the ARP monitor is not available in this mode.