e28bc14765
Currently, based on hns3 network engine, driver always reports the incoming packet's VLAN tags to the structure rte_mbuf those are the output parameter pointers in '.rx_pkt_burst' ops implementation function, and never reports PKT_RX_VLAN_STRIPPED flag to the structure rte_mbuf even if Upper Level Process configured hardware strip by calling rte_eth_dev_configure or rte_eth_dev_set_vlan_offload API function. It makes the ULP unable to know the stripping of VLAN. It is supposed to present the stripped flags to the mbuf ol_flags, and report the right VLAN tag. And as hardware constraints, the stripped VLAN tag will always in the Rx descriptor. Even if setting a PVID based on the function, the PVID will be reported to the Rx descriptor. So the driver need to determine which VLAN tag should be reported to output the structure rte_mbuf in '.rx_pkt_burst' ops implementation function named hns3_recv_pkts. Fixes: |
||
|---|---|---|
| .ci | ||
| app | ||
| buildtools | ||
| config | ||
| devtools | ||
| doc | ||
| drivers | ||
| examples | ||
| kernel | ||
| lib | ||
| license | ||
| mk | ||
| usertools | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| ABI_VERSION | ||
| GNUmakefile | ||
| MAINTAINERS | ||
| Makefile | ||
| meson_options.txt | ||
| meson.build | ||
| README | ||
| VERSION | ||
DPDK is a set of libraries and drivers for fast packet processing. It supports many processor architectures and both FreeBSD and Linux. The DPDK uses the Open Source BSD-3-Clause license for the core libraries and drivers. The kernel components are GPL-2.0 licensed. Please check the doc directory for release notes, API documentation, and sample application information. For questions and usage discussions, subscribe to: users@dpdk.org Report bugs and issues to the development mailing list: dev@dpdk.org