diff options
| author | Eddie Phillips <eddiephillips@google.com> | 2026-09-24 00:42:51 +0000 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-09-24 10:56:59 -0700 |
| commit | 3b430ea6234087957b0d3cd181e3116722b59819 (patch) | |
| tree | 0f861c1c8f08498ad4c8fc89fc79dfd0222ce039 /tools/perf/scripts/python | |
| parent | 83769c23fb1879edc916a526ba424285033baf2d (diff) | |
| download | linux-next-3b430ea6234087957b0d3cd181e3116722b59819.tar.gz linux-next-3b430ea6234087957b0d3cd181e3116722b59819.zip | |
gve: fix TX drop when GSO MSS is too small for hw
The device has a strict requirement that the minimum MSS
(gso_size) for TSO/GSO packets must be at least 88 bytes. If a packet
below this threshold is pushed to the hardware, it can cause
hardware to silently drop the packet, leading to increased latency
and retransmissions.
Currently, this is validated too late in the transmit pipeline
(gve_prep_tso), leading to silent drops.
Fix this by moving the validation into the .ndo_features_check
callback (gve_features_check_dqo). If we detect a GSO packet with
a gso_size smaller than GVE_TX_MIN_TSO_MSS_DQO, we clear the GSO
feature flags for this packet.
Fixes: a57e5de476be ("gve: DQO: Add TX path")
Signed-off-by: Eddie Phillips <eddiephillips@google.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Harshitha Ramamurthy <hramamurthy@google.com>
Link: https://patch.msgid.link/20260924004252.1196328-2-edumazet@google.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
