You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bond Port Response Traffic Imbalance with Mellanox CX4/CX5 NICs After Applying dpdk20.11 Patch 0007-bonding-device-sends-packets-with-user-specified-sal.patch
#1016
Open
panzhengyu opened this issue
Feb 2, 2025
· 0 comments
When using Mellanox ConnectX-4 or ConnectX-5 NICs with DPVS 1.9.8 under the following configuration:
DPDK 20.11 with patch 0007-bonding-device-sends-packets-with-user-specified-sal.patch applied Bonding mode configured with LACP (802.3ad) Bonding hash policy is layer34
Observed Behavior:
Response Traffic is unevenly distributed across wan bond ports, with all traffic hashed to a single interface despite two active slaves. Lan bond ports are normal.
The imbalance appears to be introduced by the DPDK 20.11 patch 0007-bonding-device-sends-packets-with-user-specified-sal.patch . Reverting this patch resolves the issue, restoring proper hash distribution across bond ports.
With this patch, ixege driver interface intel 82599 not found imbalance.
The text was updated successfully, but these errors were encountered:
Description:
When using Mellanox ConnectX-4 or ConnectX-5 NICs with DPVS 1.9.8 under the following configuration:
DPDK 20.11 with patch 0007-bonding-device-sends-packets-with-user-specified-sal.patch applied
Bonding mode configured with LACP (802.3ad)
Bonding hash policy is layer34
Observed Behavior:
Response Traffic is unevenly distributed across wan bond ports, with all traffic hashed to a single interface despite two active slaves. Lan bond ports are normal.
The imbalance appears to be introduced by the DPDK 20.11 patch 0007-bonding-device-sends-packets-with-user-specified-sal.patch . Reverting this patch resolves the issue, restoring proper hash distribution across bond ports.
With this patch, ixege driver interface intel 82599 not found imbalance.
The text was updated successfully, but these errors were encountered: