From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1097] i40e: TSO breaks when MSS spans more than 8 data fragments
Date: Tue, 11 Oct 2022 09:41:02 +0000 [thread overview]
Message-ID: <bug-1097-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1097
Bug ID: 1097
Summary: i40e: TSO breaks when MSS spans more than 8 data
fragments
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: ---
We've been running opensource ethdev tests [1] lately and we've come across a
bug in TSO:
https://ts-factory.io/bublik/v2/log/100333?focusId=102700&mode=treeAndinfoAndlog
.
In the above example, a TSO transaction with MSS=4000 is requested for a packet
bearing 6000 bytes of payload, with the first 4000 bytes spanning data located
in 13 mbuf segments. As a result, no packets are seen on the opposite end of
the wire, and the following log is produced:
i40e_dev_alarm_handler(): ICR0: malicious programming detected
i40e_handle_mdd_event(): Malicious Driver Detection event 0x02 on TX queue 1 PF
number 0x00 VF number 0x00 device 0000:01:00.0
i40e_handle_mdd_event(): TX driver issue detected on PF
According to
https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/intel/i40e/i40e_txrx.c#L3416
, the "HW can't DMA more than 8 buffers to build a packet on the wire". By the
looks of it, Tx prepare method in the PMD turns a blind eye to crossing this
boundary. Hence the error.
Apparrently, Tx prepare in i40e shall either turn such transactions down or
linearise the superframe data to some extent.
[1] http://mails.dpdk.org/archives/dev/2022-October/251663.html
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-10-11 9:41 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-1097-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