From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1476] Frame Overhead Inconsistencies Within Drivers
Date: Mon, 01 Jul 2024 16:45:07 +0000 [thread overview]
Message-ID: <bug-1476-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1476
Bug ID: 1476
Summary: Frame Overhead Inconsistencies Within Drivers
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: npratte@iol.unh.edu
Target Milestone: ---
There are inconsistencies within DPDK network drivers regarding how it
calculates Ethernet overhead. These calculations have meaningful impacts
towards how we write test suites to assess the ethdev API, namely MTUs.
Network drivers base their implementations of rte_ethdev's set_mtu() on
arbitrary Ethernet overhead constants specific to the individual network
driver. For example, the file bnxt_ethdev.c assumes an Ethernet overhead of the
standard 14 byte Ether header, CRC, and space for QinQ; i40e makes the same
assumptions. Mellanox, however, assumes only for a 14 byte Ether header plus
CRC, so the overall Ether overhead is different between NICs. DPDK drops or
forwards packets based on the total frame size, not the L3 packet/MTU size. So,
the result is that we can set the MTU the same way for different devices and
see different behavior.
If we want to, for example, test MTUs without concern for individual behavior,
then we need to discuss what the proper amount of assumed overhead is before we
can consider it a bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3471 bytes --]
reply other threads:[~2024-07-01 16:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1476-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).