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.
