From: Alex Kiselev <kiselev99@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] link bonding driver, lacp mode
Date: Wed, 28 Jun 2017 13:52:05 +0300 [thread overview]
Message-ID: <CAMKNYbzqu5dQR=92Fcd=JChywBRTPBqTueL+inzqox4JU=arVw@mail.gmail.com> (raw)
Hi.
I have a couple of questionts abount the link bonding driver.
I am using Link Aggregation 802.3AD (mode 4) of the driver.
Bonding ports are created using the EAL Command Line parameters.
A bond port works fine for some time (about one day), then it stops
forwarding packets.
Recreating aggregation group on the switch doesn't help. The only way that helps
in that situation is restarting my application. Last messages in the syslog are:
Jun 26 21:48:35 router the_router.lag[4917]: PMD: Bond 3: slave id 1
distributing started.
Jun 26 21:49:01 router the_router.lag[4917]: PMD: Bond 3: slave id 0
distributing started.
Jun 28 16:19:00 router the_router.lag[4917]: PMD: Bond 3: slave id 1
distributing started.
Jun 28 16:33:18 router the_router.lag[4917]: PMD: Bond 3: slave id 0
distributing started.
Jun 28 16:52:38 router the_router.lag[4917]: PMD: Bond 3: slave id 1
distributing started.
Jun 28 17:14:50 router the_router.lag[4917]: PMD: Bond 3: slave id 0
distributing started.
Jun 28 17:15:30 router the_router.lag[4917]: PMD: Bond 3: slave id 1
distributing started.
Jun 28 17:33:04 router the_router.lag[4917]: PMD: Bond 3: slave id 0
distributing started.
Jun 28 17:35:18 router the_router.lag[4917]: PMD: Bond 3: slave id 1
distributing started.
Jun 28 17:38:50 router the_router.lag[4917]: PMD: Bond 3: slave id 1
distributing started.
Jun 28 17:57:25 router the_router.lag[4917]: PMD: Bond 3: slave id 1
distributing started.
Jun 28 18:16:51 router the_router.lag[4917]: PMD: Bond 3: slave id 0
distributing started.
Jun 28 18:18:54 router the_router.lag[4917]: PMD: Bond 3: slave id 0
distributing started.
Jun 28 18:20:52 router the_router.lag[4917]: PMD: Bond 3: slave id 0
distributing stopped.
Jun 28 18:20:52 router the_router.lag[4917]: PMD: Bond 3: slave id 1
distributing stopped.
Jun 28 18:21:47 router the_router.lag[4917]: PMD: Bond 3: slave id 0
distributing started.
Jun 28 18:21:59 router the_router.lag[4917]: PMD: Bond 3: slave id 1
distributing started.
Jun 28 13:28:22 router the_router.lag[4917]: PMD: Bond 3: slave id 0
distributing started.
So my questionts are:
1) Is the bond driver supposed to automatically recover a bonding link
in a situation like that when pysycal links are ok?
2) What could cause a failure of a bonding link? LACPDU timeouts or drops?
3) The dpdk documentation indicates that rte_eth_tx_burst and
rte_eth_rx_burst functions should be called with intervals period of
less than 100ms.
Does it mean that the function should be called even there are no
packets to send?
What are the correct parameters for rte_eth_tx_burst function in a
case when there is no
packets to send?
Can it be called with the NULL parameter?
rte_eth_tx_burst(portid, queueid, NULL, 0);
Thank you.
Alex Kiselev.
next reply other threads:[~2017-06-28 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 10:52 Alex Kiselev [this message]
2017-06-29 10:49 Alex Kiselev
2017-06-29 13:06 ` Kyle Larose
2017-06-29 14:30 ` Alex Kiselev
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='CAMKNYbzqu5dQR=92Fcd=JChywBRTPBqTueL+inzqox4JU=arVw@mail.gmail.com' \
--to=kiselev99@gmail.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).