DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: mbuf refcnt issue
Date: Tue, 8 Apr 2025 20:53:41 -0700	[thread overview]
Message-ID: <20250408205341.68d37d0a@hermes.local> (raw)
In-Reply-To: <CH3PR01MB84701BB0789658E84AFE7FDF8FB52@CH3PR01MB8470.prod.exchangelabs.com>

On Tue, 8 Apr 2025 22:33:56 +0000
"Lombardo, Ed" <Ed.Lombardo@netscout.com> wrote:

> Hi Dmitry,
> I added mbuf refcnt check at the point where we get the packets from DPDK rte_eth_rx_burst() and I am finding many mbufs refcnt set to 2 when I expect them to be 1.  This is more evidence that something has gone wrong within DPDK and the mempool management, perhaps, and I don't know how my setup went into this state.  I changed the traffic type from Telnet to Enterprise traffic and rte_eth_tx_burst() no longer accepts mbufs. 

Not likely a DPDK bug. More likely you are having application problems.
Have you tried enabling things like RTE_LIBRTE_MBUF_DEBUG and RTE_LIBRTE_MEMPOOL_DEBUG
and RTE_ENABLE_ASSERT?

Also using a current version of DPDK, address sanitizer, and latest GCC or CLANG
can uncover issues with use after free.

  reply	other threads:[~2025-04-09  3:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 22:00 Lombardo, Ed
2025-04-04 22:29 ` Dmitry Kozlyuk
2025-04-07 19:53   ` Lombardo, Ed
2025-04-08 22:33     ` Lombardo, Ed
2025-04-09  3:53       ` Stephen Hemminger [this message]
2025-04-09  4:46         ` Lombardo, Ed
2025-04-09 16:24           ` Stephen Hemminger
2025-04-09 23:22             ` Lombardo, Ed
2025-04-10  3:25               ` Stephen Hemminger
2025-04-10  3:58                 ` Lombardo, Ed
2025-04-10 21:15                   ` Lombardo, Ed
2025-04-15 13:10                     ` Lombardo, Ed
2025-04-16  0:01                       ` Stephen Hemminger
2025-04-16  3:51                         ` Lombardo, Ed
2025-04-09 16:15       ` Lombardo, Ed

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=20250408205341.68d37d0a@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=Ed.Lombardo@netscout.com \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=users@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).