> > Adding Helin to the conversation. > > > That's a common problem across Intel VF devices. Bothe igb and ixgbe > > overcomes that problem just by forcing ' rxmode.hw_strip_crc = 1;' at > > PMD itself: > > [...] > > > Wonder, can't i40e VF do the same? > > Right, however, and this (silent failure) approach was rejected by the > maintainers. Please, refer to this thread: > http://dpdk.org/ml/archives/dev/2016-April/037523.html > > > BTW, all other examples would experience same problem too, right? > > Correct, so the broader question would be "what is the correct behavior > for an example application, when a port configuration isn't supported by > the hardware?". > > My stand, FWIW, is that igb and ixgbe should have the same semantics as > i40e currently has, i.e. return an error to the user if the port is > mis-configured, NOT changing the setting behind the users back. >
Fine by me, but then it means that the fix haw to include changes for all apps plus ixgbe and igb PMDs, correct? :) Konstantin
