b563c14212
Removing 'DEV_RX_OFFLOAD_JUMBO_FRAME' offload flag. Instead of drivers announce this capability, application can deduct the capability by checking reported 'dev_info.max_mtu' or 'dev_info.max_rx_pktlen'. And instead of application setting this flag explicitly to enable jumbo frames, this can be deduced by driver by comparing requested 'mtu' to 'RTE_ETHER_MTU'. Removing this additional configuration for simplification. Suggested-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> Reviewed-by: Rosen Xu <rosen.xu@intel.com> Acked-by: Somnath Kotur <somnath.kotur@broadcom.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Huisong Li <lihuisong@huawei.com> Acked-by: Hyong Youb Kim <hyonkim@cisco.com> Acked-by: Michal Krawczyk <mk@semihalf.com> |
||
---|---|---|
.. | ||
img | ||
avx512.rst | ||
debug_troubleshoot.rst | ||
flow_bifurcation.rst | ||
index.rst | ||
lm_bond_virtio_sriov.rst | ||
lm_virtio_vhost_user.rst | ||
openwrt.rst | ||
packet_capture_framework.rst | ||
pvp_reference_benchmark.rst | ||
rte_flow.rst | ||
telemetry.rst | ||
vfd.rst | ||
virtio_user_as_exceptional_path.rst | ||
virtio_user_for_container_networking.rst |