As the algorithm used by '3+4' "xmit_hash_policy" is not fully 802.3ad compliant, so is that policy supported to us by Red Hat ?

Solution Verified - Updated -

Issue

  • As per testing done with switch and different xmit_hash_policy on server, the best performance is achieved with '3+4' policy, although the algorithm used by this policy is not 802.3ad compliant fully. So would be supported by Red Hat to use '3+4' policy ?

Environment

  • Red Hat Enterprise Linux (Any Version)
  • Bonding with xmit_hash_policy configured

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content