From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1911] bnxt: tx checksum offload for MPLS packets
Date: Wed, 25 Mar 2026 02:31:38 +0000 [thread overview]
Message-ID: <bug-1911-3-NtJIHYlC8W@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1911-3@http.bugs.dpdk.org/>
http://bugs.dpdk.org/show_bug.cgi?id=1911
Stephen Hemminger (stephen@networkplumber.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
CC| |stephen@networkplumber.org
--- Comment #1 from Stephen Hemminger (stephen@networkplumber.org) ---
Short answer is DPDK does not support checksum for MPLS.
Longer answer:
The transmit checksum API interface in DPDK expects that any encapsulation
headers are done as transmit offloads. There is no API for devices to report
MPLS offload, and there is no driver that supports it.
If you have the hardware support, would love to see this as a future
enhancement.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2026-03-25 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 22:37 [DPDK/ethdev Bug 1911] bnxt: tx checksum offload for MPLS packets bugzilla
2026-03-25 2:31 ` bugzilla [this message]
2026-03-25 23:47 ` bugzilla
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-1911-3-NtJIHYlC8W@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