From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1296] net/mlx5 driver causing indirect pool leakage when testing IPv6 fragmentation
Date: Wed, 11 Oct 2023 08:09:42 +0000 [thread overview]
Message-ID: <bug-1296-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1296
Bug ID: 1296
Summary: net/mlx5 driver causing indirect pool leakage when
testing IPv6 fragmentation
Product: DPDK
Version: 22.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: java.liu@ericsson.com
Target Milestone: ---
When testing IPv6 fragmentation uisng net/mlx5 driver we noticed the indirect
buffer is not returning to the pool and will eventually cause indirect pool to
be exausted.
when using intel nic with iavf driver with same application code the issue is
not seen. There is also no issue for pcap driver.
when review code
https://github.com/DPDK/dpdk/blob/main/drivers/net/mlx5/mlx5_tx.h function
mlx5_tx_free_mbuf(). Seems in rte_pktmbuf_prefree_seg(*pkts) the pkts->next
will be set to NULL for indirect buffer which is linked to the direct buffer.
Test is done by explicitly putting the indirect buffer back to mem pool at end
of function mlx5_tx_free_mbuf().
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3236 bytes --]
reply other threads:[~2023-10-11 8:09 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-1296-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).