* [DPDK/ethdev Bug 1638] Differences in how different Intel NICs handle maximum packet length for jumbo frame
@ 2025-02-03 3:05 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2025-02-03 3:05 UTC (permalink / raw)
To: dev
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1638
Bug ID: 1638
Summary: Differences in how different Intel NICs handle maximum
packet length for jumbo frame
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: nandinipersad361@gmail.com
Target Milestone: ---
10 Gigabit Ethernet devices from Intel do not take VLAN tags into account when
calculating packet size while Gigabit Ethernet devices do so for jumbo frames.
Implication:
When receiving packets with VLAN tags, the actual maximum size of useful
payload that Intel Gigabit Ethernet devices are able to receive is 4 bytes (or
8 bytes in the case of packets with extended VLAN tags) less than that of Intel
10 Gigabit Ethernet devices.
Resolution/Workaround:
Increase the configured maximum packet size when using Intel Gigabit Ethernet
devices.
Affected Environment/Platform:
All.
Driver/Module:
Poll Mode Driver (PMD).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3142 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-02-03 3:05 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-02-03 3:05 [DPDK/ethdev Bug 1638] Differences in how different Intel NICs handle maximum packet length for jumbo frame bugzilla
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.