Firstly, sorry about the late reply. > From my view, crc-strip is not a "MUST" check for the port start. We can > configure the value after > the port start. > Any thoughts?
>From my perspective, a non-supported configuration should return an error code to the API user. > Do you know is there any way I can bypass this when I use l3fwd? One work-around is enabling .hw_strip_crc for i40 VFs at runtime, by e.g. using rte_eth_dev_info_get() to determine what driver that's in use. That, however, does require a l3fwd patch. Bj?rn
