DPDK bond mode 4 cares about the boot sequence of the slave device

DPDK bond mode 4 cares about the boot sequence of the slave device

[Hong Christian]

[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]

Hello DPDK users,

I met an issue while testing dpdk bond mode 4: the net_bonding vdev cannot work while the slave devices boot sequence is not same as EAL parameters configuration.

I create my bonding vdev by EAL parameters: "--file-prefix rte --log-level pmd.net.bond:debug --vdev net_bonding0,mode=4,slave=0000:01:00.0,slave=0000:02:00.0"
Thus we have:
port0 = "0000:01:00.0"
port1 = "0000:02:00.0"

Success senario:

  1.  port0 ready then port 1 ready;

"
bond_mode_8023ad_register_lacp_mac(951) - forced allmulti for port 0
bond_mode_8023ad_register_lacp_mac(951) - forced allmulti for port 1
mux_machine(532) - Bond 4: slave id 0 distributing started.
mux_machine(532) - Bond 4: slave id 1 distributing started.
"

  1.  After bonding successfully, port1 down and up, it could be in bond state again

Fail senario:

  1.  port 1 ready then port 0 ready (all in suspend state)

"
bond_mode_8023ad_register_lacp_mac(951) - forced allmulti for port 1
bond_mode_8023ad_register_lacp_mac(951) - forced allmulti for port 0
/* then no distributing started prints */
"

  1.  After bonding successfully, port 0 down and up( then port 0 will stay in suspend state)

ENV:
DPDK: v19.11.6
Switch config: lacp passive mode, same priority for the connected two ports

Does any one met the same issue ? Is this a dpdk bond bug ? Hope to receive your response. Thanks in advance.

Br,
Christian

[-- Attachment #2: Type: text/html, Size: 5979 bytes --]