Ferruh Yigit 411878ba25 net/memif: fix driver init with default MTU ... Driver is using 'ETH_FRAME_LEN' Linux defined value as max frame length, which doesn't include FCS (4 bytes CRC). But ethdev by default uses frame size with FCS when application doesn't define any explicit value. As a result device configuration fails because device is tried to be configured with a frame size length that is bigger than what device reported as supported. Device reports as max supported frame size is 1514 but configured value is 1518. Instead use DPDK macro, 'RTE_ETHER_MAX_LEN', that includes FCS in the driver to report the max supported frame size, this matches to the initial intention. Fixes: 1bb4a528c4 ("ethdev: fix max Rx packet length") Reported-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Tested-by: David Christensen <drc@linux.vnet.ibm.com> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>		2021-10-27 17:48:51 +02:00
..
memif_socket.c	drivers: remove direct access to interrupt handle	2021-10-25 21:20:12 +02:00
memif_socket.h	drivers: remove direct access to interrupt handle	2021-10-25 21:20:12 +02:00
memif.h	net/memif: replace master/slave arguments	2020-10-20 13:17:08 +02:00
meson.build	drivers: change indentation in build files	2021-04-21 14:04:09 +02:00
rte_eth_memif.c	net/memif: fix driver init with default MTU	2021-10-27 17:48:51 +02:00
rte_eth_memif.h	drivers: remove direct access to interrupt handle	2021-10-25 21:20:12 +02:00
version.map	version: 21.11-rc0	2021-08-17 08:37:52 +02:00