From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1342] net/i40e rejects packet without any Tx offload on Tx prepare
Date: Fri, 05 Jan 2024 12:57:11 +0000 [thread overview]
Message-ID: <bug-1342-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1342
Bug ID: 1342
Summary: net/i40e rejects packet without any Tx offload on Tx
prepare
Product: DPDK
Version: 23.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: andrew.rybchenko@oktetlabs.ru
Target Milestone: ---
net/i40e rejects packet without any Tx offload on Tx prepare
Tx is configured to use no offloads. So, simple Tx prepare callback is used by
the driver.
mbuf has the following flags set: TX_L4_NO_CKSUM |TX_IPV4 | TX_OUTER_IPV4 |
TX_TUNNEL_VXLAN | RX_IP_CKSUM_UNKNOWN | RX_L4_CKSUM_UNKNOWN
See logs
https://ts-factory.io/bublik/v2/log/362398?focusId=368929&mode=treeAndinfoAndlog&experimental=true&lineNumber=1_70
These flags do not request any Tx offloads, just specify that it is a VXLAN
packet with inner and outer IPv4.
However, Tx prepare rejects it:
https://ts-factory.io/bublik/v2/log/362398?focusId=368929&mode=treeAndinfoAndlog&experimental=true&lineNumber=1_89
Above logs are result of the test suite run at UNH IOL.
I guess the problem is TX_TUNNEL_VXLAN. I guess addition of
RTE_MBUF_F_TX_TUNNEL_MASK to I40E_TX_OFFLOAD_SIMPLE_SUP_MASK will solve the
problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3656 bytes --]
reply other threads:[~2024-01-05 12:57 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-1342-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).