On 12/9/2020 3:16 AM, Steve Yang wrote:
The jumbo frame used the 'RTE_ETHER_MAX_LEN' as boundary condition, this
fix will change the boundary condition with 'RTE_ETHER_MTU'.
When the MTU(1500) set, the frame type of rx packet will be different
if used different overhead, it will cause the consis
Hi, steve
What I saw is that you replace of frame size checking to mtu checking, but you
still use
"18" as overhead number to configure max_rx_pkt_len?
uint32_t frame_size = mtu + RTE_ETHER_HDR_LEN + RTE_ETHER_CRC_LEN;
dev->data->dev_conf.rxmode.max_rx_pkt_len = frame_size;
> -Original Me
The jumbo frame used the 'RTE_ETHER_MAX_LEN' as boundary condition, this
fix will change the boundary condition with 'RTE_ETHER_MTU'.
When the MTU(1500) set, the frame type of rx packet will be different
if used different overhead, it will cause the consistency issue, and the
normal packet will be
3 matches
Mail list logo