From: Hong Christian <hongguochun@hotmail.com>
To: "users@dpdk.org" <users@dpdk.org>,
Pawel Wodkowski <pawelx.wodkowski@intel.com>
Subject: DPDK bond mode 4 cares about the boot sequence of the slave device
Date: Wed, 1 Dec 2021 09:36:05 +0000 [thread overview]
Message-ID: <SY4P282MB2758AC213AB12AA086D83D84AC689@SY4P282MB2758.AUSP282.PROD.OUTLOOK.COM> (raw)
[-- 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 --]
reply other threads:[~2021-12-01 9:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SY4P282MB2758AC213AB12AA086D83D84AC689@SY4P282MB2758.AUSP282.PROD.OUTLOOK.COM \
--to=hongguochun@hotmail.com \
--cc=pawelx.wodkowski@intel.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).