From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1910] bnxt: RTE_ETH_TX_OFFLOAD_VLAN_INSERT doesn't insert vlan
Date: Tue, 24 Mar 2026 11:54:09 +0000 [thread overview]
Message-ID: <bug-1910-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1910
Bug ID: 1910
Summary: bnxt: RTE_ETH_TX_OFFLOAD_VLAN_INSERT doesn't insert
vlan
Product: DPDK
Version: 25.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: oleksandrn@interfacemasters.com
Target Milestone: ---
On 57608, RTE_ETH_TX_OFFLOAD_VLAN_INSERT doesn't seem to be working; it is
reported as a supported capability, but the VLAN is not actually added. The
same codebase works with other nics.
I also tried testpmd
port stop 0
port config 0 tx_offload vlan_insert on
tx_vlan set 0 133
port start 0
start tx_first 1
I don't see VLAN on the other side.
As far as I remember, when TruFlow is enabled, 57608 doesn't support VLAN
stripping, so maybe it is the same case for VLAN insertion as well, but then
RTE_ETH_TX_OFFLOAD_VLAN_INSERT shouldn't be reported as supported by pmd,
haven't tried without TruFlow.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-03-24 11:54 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-1910-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 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.