From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 949] net/mlx5: errors when sending from extbuf pool
Date: Fri, 04 Mar 2022 13:41:53 +0000 [thread overview]
Message-ID: <bug-949-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=949
Bug ID: 949
Summary: net/mlx5: errors when sending from extbuf pool
Product: DPDK
Version: 21.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: bmerry@sarao.ac.za
Target Milestone: ---
Created attachment 193
--> https://bugs.dpdk.org/attachment.cgi?id=193&action=edit
Example code
Given the lack of documentation it's likely that I'm just holding it wrong, but
I'm having trouble when trying to transmit segmented packets where one of the
segments is from a pool created with rte_pktmbuf_pool_create_extbuf.
I've reduced my test to the attached program. The test builds and transmits
multicast UDP (IPv4) frames. The L2-L4 headers are in a regular mbuf, chained
to a separate mbuf holding the payload. If the USE_EXTERNAL define at the top
is changed to 0, the payload mbuf is a boring standard mbuf, and everything
works and I can receive the packets on another machine. When USE_EXTERNAL=1, a
single huge page is allocated with mmap, then used to back the mempool for
payloads (via rte_pktmbuf_pool_create_extbuf). In this case, I get a whole
bunch of files written with names like
dpdk_mlx5_port_0_txq_0_index_0_1383899876, reporting CQ and SQ errors, and I
don't receive the packets (and the tx ethtool counters don't go up).
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-03-04 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 13:41 bugzilla [this message]
2022-03-13 11:30 ` 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-949-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).