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 a
+ dpdk.org mailing list. I also thought the patch to check port CRC strip then
make the port fail to start is not proper.
For testpmd, we can use -crc-strip, but for l3fwd, we may need change code to
enable crc-strip, and for all application, we need change the code; this is not
acceptable.
User
2 matches
Mail list logo
