| Message ID | 20220406135420.21682-1-gal@nvidia.com (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | 2cd1881b9821be68d1eb748c96311258b16af225 |
| Delegated to: | Netdev Maintainers |
| Headers | show |
| Series | bonding: Update layer2 and layer2+3 hash formula documentation | expand |
Hello: This patch was applied to netdev/net.git (master) by David S. Miller <davem@davemloft.net>: On Wed, 6 Apr 2022 16:54:20 +0300 you wrote: > When using layer2 or layer2+3 hash, only the 5th byte of the MAC > addresses is used. > > Signed-off-by: Gal Pressman <gal@nvidia.com> > --- > Documentation/networking/bonding.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) Here is the summary with links: - bonding: Update layer2 and layer2+3 hash formula documentation https://git.kernel.org/netdev/net/c/2cd1881b9821 You are awesome, thank you!
diff --git a/Documentation/networking/bonding.rst b/Documentation/networking/bonding.rst index 525e6842dd33..43be3782e5df 100644 --- a/Documentation/networking/bonding.rst +++ b/Documentation/networking/bonding.rst @@ -894,7 +894,7 @@ xmit_hash_policy Uses XOR of hardware MAC addresses and packet type ID field to generate the hash. The formula is - hash = source MAC XOR destination MAC XOR packet type ID + hash = source MAC[5] XOR destination MAC[5] XOR packet type ID slave number = hash modulo slave count This algorithm will place all traffic to a particular @@ -910,7 +910,7 @@ xmit_hash_policy Uses XOR of hardware MAC addresses and IP addresses to generate the hash. The formula is - hash = source MAC XOR destination MAC XOR packet type ID + hash = source MAC[5] XOR destination MAC[5] XOR packet type ID hash = hash XOR source IP XOR destination IP hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 8)
When using layer2 or layer2+3 hash, only the 5th byte of the MAC addresses is used. Signed-off-by: Gal Pressman <gal@nvidia.com> --- Documentation/networking/bonding.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)