Re: [PATCH] net/gve: Update max_rx_pktlen to be based on MTU

2023-10-26 Thread Ferruh Yigit
On 10/16/2023 9:59 PM, Joshua Washington wrote: > Before this patch, max_rx_pktlen was always set to UINT16_MAX. This, in > conjunction with the MTU fix, causes problems with testpmd, as setting the > packet length with the --max-pkt-len flag causes the MTU to be set > higher than possible due to u

Re: [PATCH] net/gve: Update max_rx_pktlen to be based on MTU

2023-10-16 Thread Stephen Hemminger
On Mon, 16 Oct 2023 13:59:48 -0700 Joshua Washington wrote: > conjunction with the MTU fix, causes problems with testpmd, as setting the > packet length with the --max-pkt-len flag causes the MTU to be set > higher than possible due to underflow. > > As an example, setting --max-pkt-len=1460 (th

Re: [PATCH] net/gve: Update max_rx_pktlen to be based on MTU

2023-10-16 Thread Stephen Hemminger
On Mon, 16 Oct 2023 13:59:48 -0700 Joshua Washington wrote: > Before this patch, max_rx_pktlen was always set to UINT16_MAX. This, in > conjunction with the MTU fix, causes problems with testpmd, as setting the > packet length with the --max-pkt-len flag causes the MTU to be set > higher than pos

[PATCH] net/gve: Update max_rx_pktlen to be based on MTU

2023-10-16 Thread Joshua Washington
Before this patch, max_rx_pktlen was always set to UINT16_MAX. This, in conjunction with the MTU fix, causes problems with testpmd, as setting the packet length with the --max-pkt-len flag causes the MTU to be set higher than possible due to underflow. As an example, setting --max-pkt-len=1460 (th