Hi,
Basically, you have to make sure you call rte_eth_tx_burst() every 100
ms in your forwarding loop. Here is such an example:
const uint64_t bond_tx_cycles = (rte_get_timer_hz() + MS_PER_S - 1) *
100 / MS_PER_S;
uint64_t cur_bond_cycles, diff_cycles;
uint64_t last_bond_tx_cycles = 0;
/* Inside your forwarding loop: */
cur_bond_cycles = rte_get_timer_cycles();
diff_cycles = cur_bond_cycles - last_bond_tx_cycles;
if (diff_cycles > bond_tx_cycles) {
last_bond_tx_cycles = cur_bond_cycles;
rte_eth_tx_burst(bond_port_id, 0, NULL, 0);
}
There is a user at dpdk.org mailing list, please address such questions there.
Regards,
Andriy
On Sat, Apr 16, 2016 at 11:41 AM, yangbo <yangbo_588 at outlook.com> wrote:
> Hi,
>
> How to understand bond api comments:
>
> for LACP mode to work the rx/tx burst functions must be invoked at least once
> every 100ms, otherwise the out-of-band LACP messages will not be handled with
> the expected latency and this may cause the link status to be incorrectly
> marked as down or failure to correctly negotiate with peers.
>
>
> can any one give me example or more detail info ?
>
> I am extremely grateful for it.
--
Andriy Berestovskyy
