From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/testpmd Bug 1777] --max-pkt-len below 1500 does not seem to to be enforced
Date: Thu, 21 Aug 2025 02:44:11 +0000 [thread overview]
Message-ID: <bug-1777-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1777
Bug ID: 1777
Summary: --max-pkt-len below 1500 does not seem to to be
enforced
Product: DPDK
Version: 22.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: canary.overflow@gmail.com
Target Milestone: ---
I observed that setting --max-pkt-len to a value lower than 1500 does not
enforce this value even though "show port info X" showed that the MTU was set
to the value passed in.
(e.g. packets larger than 800 bytes (> 1000 bytes) were still observed even
though --max-pkt-len=800 was set)
I believe that there is a default value that --max-pkt-len falls back on if the
value is too low. If this is the case, this value should also be reflected in
the port info.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2926 bytes --]
reply other threads:[~2025-08-21 2:44 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-1777-3@https.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).