From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1367] net/mlx5 Tx stuck if mbuf has too many segments
Date: Thu, 18 Jan 2024 07:28:37 +0000 [thread overview]
Message-ID: <bug-1367-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1367
Bug ID: 1367
Summary: net/mlx5 Tx stuck if mbuf has too many segments
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/mlx5 Tx stuck if mbuf has too many segments
net/mlx5 reports maximum number of Tx segments in device info, but it does not
check it on Tx prepare and simply do not send it on Tx burst.
As the result if such packet is encountered, app does not know (without extra
efforts) why it fails to send the packet after successful Tx prepare. In theory
the reason could be fully occupied Tx queue and application should simply retry
forever.
Found by test run at UNH IOL:
1. Test checks reported maximum segments count: tx_desc_lim.nb_mtu_seg_max=40
https://ts-factory.io/bublik/v2/log/477842?focusId=479564&mode=treeAndinfoAndlog&experimental=true&lineNumber=1_25
2. Test splits the packet into 60 segments:
https://ts-factory.io/bublik/v2/log/477842?focusId=479564&mode=treeAndinfoAndlog&experimental=true&lineNumber=1_49
3. Test logs expectations for the packet to be rejected by Tx prepare:
https://ts-factory.io/bublik/v2/log/477842?focusId=479564&mode=treeAndinfoAndlog&experimental=true&lineNumber=1_60
4. Tx prepare accepts the packet and the test logs error:
https://ts-factory.io/bublik/v2/log/477842?focusId=479564&mode=treeAndinfoAndlog&experimental=true&lineNumber=1_62
5. Test tries to Tx burst the packet, but it returns 0. One more error is
logged.
https://ts-factory.io/bublik/v2/log/477842?focusId=479564&mode=treeAndinfoAndlog&experimental=true&lineNumber=1_62
IMHO better behaviour here would be to accept the packet bug simply drop it in
SW on Tx before passing to HW. Just avoid Tx stuck.
Of course Tx prepare should reject the packet at step 4.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4795 bytes --]
reply other threads:[~2024-01-18 7:28 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-1367-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).