Hi All:
This patch fixes a issue when DPDK 802.3ad bonding rx_machine enters EXPIRED
state, but the opposite SWITCH lacp ignores distributing and collecting bit, so
the SWITCH still sends packets to DPDK and all these packets are dropped.
diff --git a/drivers/net/bonding/rte_eth_bond_8023ad.c
b
Why doesn’t DPDK support `DEFAULTED` state in Receive machine in 802.3ad bond
implementation?
Why doesn’t DPDK support `DEFAULTED` state in Receive machine in 802.3ad bond
implementation?
I mean DPDK APIs do not exclude ipv4 options or ipv6 extension headers, it is
bug?
发件人: Shyam Shrivastav [mailto:shrivastav.sh...@gmail.com]
发送时间: 2018年10月20日 13:23
收件人: lidejun
抄送: users ; dev@dpdk.org; Lichunhe (Cloud Networking)
; Wangliefeng
主题: Re: [dpdk-dev] IPV4/IPV6 TCP/UDP Pseudo
Has anybody used the following two APIs calculating ipv4&ipv6 tcp/udp pseudo
header checksum?
1.rte_ipv4_phdr_cksum
2.rte_ipv6_phdr_cksum
The ipv4 version does not exclude ip options and ipv6 version does not exclude
extersion headers.
5 matches
Mail list logo