From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1125] i40e: Tx offload for outer UDP checksum is advertised but in fact unsupported
Date: Sat, 12 Nov 2022 12:15:24 +0000 [thread overview]
Message-ID: <bug-1125-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1125
Bug ID: 1125
Summary: i40e: Tx offload for outer UDP checksum is advertised
but in fact unsupported
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: ivan.malov@oktetlabs.ru
Target Milestone: ---
In the opensource ethdev verification suite [1], there is a test,
xmit/one_packet, which is tailored specifically for Tx offload checks. In the
case of i40e, the test finds a bug in encap. TSO support.
As shown in [2], a VXLAN packet with TSO request is transmitted, and resulting
packets mismatch because of the wrong checksum in the outer UDP header (it is
the same as the one in the original superframe). However, since the test sees
capability bit TX_OFFLOAD_OUTER_UDP_CKSUM in device info, the checksum is
expected to be offloaded.
According to Intel(R) Ethernet Controller X710/ XXV710/XL710 Datasheet, section
8.4.4.2, "Tunneling UDP headers and GRE header are not offloaded while the
X710/XXV710/XL710 leaves their checksum field as is". That means the i40e PMD
shall not advertise TX_OFFLOAD_OUTER_UDP_CKSUM capability via device info API.
[1] https://mails.dpdk.org/archives/dev/2022-October/251663.html
[2] https://ts-factory.io/bublik/v2/log/163204?focusId=165783&mode=treeAndlog
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-11-12 12:15 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-1125-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).