From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1134] net/i40e Tx prepare unexpectedly rejects packet with tunnel type set and no offloads requested
Date: Wed, 30 Nov 2022 07:19:36 +0000 [thread overview]
Message-ID: <bug-1134-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1134
Bug ID: 1134
Summary: net/i40e Tx prepare unexpectedly rejects packet with
tunnel type set and no offloads requested
Product: DPDK
Version: 22.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 Tx prepare unexpectedly rejects packet with tunnel type set and no
offloads requested
Tunnel type (e.g. RTE_MBUF_F_TX_TUNNEL_VXLAN) is just an auxiliary information
which does not request any Tx offload itself (similar to RTE_MBUF_F_TX_IPV4).
So, if a packet has the tunnel type set it should not be rejected by
i40e_simple_prep_pkts() as unsupported offload requested. I.e.
RTE_MBUF_F_TX_TUNNEL_MASK should be included in
I40E_TX_OFFLOAD_SIMPLE_SUP_MASK.
Found using [1]. Line 48 [2] sets ol_flags. Line 79 [3] shows that the packet
is rejected by Tx prepare. Requested Tx offload can be found in line 31 [4]
[1]
https://ts-factory.io/bublik/v2/log/243407?focusId=249938&mode=treeAndinfoAndlog
[2]
https://ts-factory.io/logs/2022/11/29/balin-x710-p0-22/html/node_id6531.html#line48
[3]
https://ts-factory.io/logs/2022/11/29/balin-x710-p0-22/html/node_id6531.html#line79
[3]
https://ts-factory.io/logs/2022/11/29/balin-x710-p0-22/html/node_id6531.html#line31
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-11-30 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 7:19 bugzilla [this message]
2022-11-30 7:20 ` [Bug 1134] net/i40e Tx prepare unexpectedly rejects packet with tunnel type set and no offloads requested 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-1134-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.