50ce3e7aec
Currently, there is a potential problem that calling the API function rte_eth_dev_set_vlan_offload to start VLAN hardware offloads which the driver does not support. If the PMD driver does not support certain VLAN hardware offloads and does not check for it, the hardware setting will not change, but the VLAN offloads in dev->data->dev_conf.rxmode.offloads will be turned on. It is supposed to check the hardware capabilities to decide whether the relative callback needs to be called just like the behavior in the API function named rte_eth_dev_configure. And it is also needed to cleanup duplicated checks which are done in some PMDs. Also, note that it is behaviour change for some PMDs which simply ignore (with error/warning log message) unsupported VLAN offloads, but now it will fail. Fixes: |
||
|---|---|---|
| .. | ||
| base | ||
| enic_clsf.c | ||
| enic_compat.h | ||
| enic_ethdev.c | ||
| enic_flow.c | ||
| enic_fm_flow.c | ||
| enic_main.c | ||
| enic_res.c | ||
| enic_res.h | ||
| enic_rxtx_common.h | ||
| enic_rxtx_vec_avx2.c | ||
| enic_rxtx.c | ||
| enic.h | ||
| Makefile | ||
| meson.build | ||
| rte_pmd_enic_version.map | ||