From: "Алексей Телятников" <at@spmail.ru>
To: users@dpdk.org
Subject: [dpdk-users] Does BONDING_MODE_8023AD is works in 17.11?
Date: Sat, 18 Nov 2017 01:24:08 +0300 [thread overview]
Message-ID: <c77b088c-58e0-4f21-f703-3e6519f97978@spmail.ru> (raw)
Greetings. I have issue with link-aggregation in DPDK. My HP A5820X
switch does not recive LACP from DPDK application.
Has anyone worked with BONDING_MODE_8023AD?
I have: DPDK 17.11 HEAD & 11.1-RELEASE-p4 FreeBSD
Also I build examples/bond with little changes:
--- a/examples/bond/main.c
+++ b/examples/bond/main.c
@@ -226,7 +226,7 @@ bond_port_init(struct rte_mempool *mbuf_pool)
uint16_t nb_rxd = RTE_RX_DESC_DEFAULT;
uint16_t nb_txd = RTE_TX_DESC_DEFAULT;
- retval = rte_eth_bond_create("bond0", BONDING_MODE_ALB,
+ retval = rte_eth_bond_create("net_bonding0", BONDING_MODE_8023AD,
0 /*SOCKET_ID_ANY*/);
if (retval < 0)
rte_exit(EXIT_FAILURE,
Run it:
$ sudo build/bond_app
EAL: Sysctl reports 16 cpus
EAL: Detected 16 lcore(s)
EAL: Contigmem driver has 1 buffers, each of size 32GB
EAL: Mapped memory segment 1 @ 0x8023ff000: physaddr:0x800000000, len
34359738368
EAL: PCI device 0000:03:00.0 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: 0000:03:00.0 not managed by UIO driver, skipping
EAL: PCI device 0000:03:00.3 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: 0000:03:00.3 not managed by UIO driver, skipping
EAL: PCI device 0000:05:00.0 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:05:00.1 on NUMA socket 0
EAL: probe driver: 8086:10fb net_ixgbe
User device list:
PMD: ixgbe_dev_link_status_print(): Port 0: Link Down
Port 0 MAC: 90:e2:ba:d0:a3:c4
PMD: ixgbe_dev_link_status_print(): Port 1: Link Down
Port 1 MAC: 90:e2:ba:d0:a3:c5
EAL: Initializing pmd_bond for net_bonding0
PMD: Using mode 4, it is necessary to do TX burst and RX burst at least
every 100ms.
EAL: Create bonded device net_bonding0 on port 2 in mode 4 on socket 0.
PMD: ixgbe_dev_link_status_print(): Port 0: Link Down
PMD: ixgbe_dev_link_status_print(): Port 1: Link Down
Port 2 MAC: 90:e2:ba:d0:a3:c4
Starting lcore_main on core 1:0 Our IP:7.0.0.10
bond6>show
90:e2:ba:d0:a3:c4
90:e2:ba:d0:a3:c5
Active_slaves:0 packets received:Tot:0 Arp:0 IPv4:0
Active slaves always 0. I tried configure bond in testpmd. Same problem.
On the switch all ports is in up state but:
Received LACP Packets: 0 packet(s)
next reply other threads:[~2017-11-17 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 22:24 Алексей Телятников [this message]
2018-01-18 14:14 ` Thomas Monjalon
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=c77b088c-58e0-4f21-f703-3e6519f97978@spmail.ru \
--to=at@spmail.ru \
--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).