DPDK usage discussions
 help / color / mirror / Atom feed
From: "Jaiswal, Adesh" <adesh.jaiswal@rakuten.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Issue with Packet Memory Allocation – Double Allocation Without Freeing
Date: Wed, 26 Mar 2025 16:51:39 +0000	[thread overview]
Message-ID: <TYYP286MB1619DCDDD33B65C8037F0744F9A62@TYYP286MB1619.JPNP286.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

Hello everyone,

We are using memory allocation for packets in our DPDK-based application. However, we are observing a de-sync issue where, during debugging, we see logs indicating that a packet is allocated twice without being freed in between.
To diagnose the issue, we added logging at both the time of allocation and deallocation. From the logs, we noticed:

  *   The same memory address is allocated/shared twice without a corresponding free operation.
  *   This is causing inconsistencies in packet handling.
Our Questions:

  1.  Is this a known issue in DPDK 18.08?
  2.  Is there any existing patch or workaround available for this problem?
  3.  What could cause a scenario where a packet is allocated twice without freeing?
  4.  What debugging approaches or tools would you recommend for tracking such memory allocation inconsistencies?
Additional Details:

  *   DPDK version: DPDK 18.08.0 version 16
Would appreciate any insights or debugging tips from the community!

Thanks,
Adesh


[-- Attachment #2: Type: text/html, Size: 8662 bytes --]

             reply	other threads:[~2025-03-26 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 16:51 Jaiswal, Adesh [this message]
2025-03-26 19:23 ` Stephen Hemminger

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=TYYP286MB1619DCDDD33B65C8037F0744F9A62@TYYP286MB1619.JPNP286.PROD.OUTLOOK.COM \
    --to=adesh.jaiswal@rakuten.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).