From: Gokilavani A <gokilavanianbazhagan@gmail.com>
To: users@dpdk.org
Subject: Re: rte_pktmbuf_alloc( ) returns same mbuf address which is not freed
Date: Tue, 25 Oct 2022 14:11:26 +0530 [thread overview]
Message-ID: <CAFYD4LqCO7qo0Oa-HpMqqLS+Y94u8W69zn2O261us5y=c=5G6g@mail.gmail.com> (raw)
In-Reply-To: <CAFYD4LqhoX7UC2z0bpeYg2Hb6xcdTOVP61CRMTtt9wHjtqqD5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
Hi,
We have been blocked by this issue.
Can anyone help us to resolve the issue?
Thanks
Gokilavani A
On Thu, Oct 13, 2022 at 4:39 PM Gokilavani A <gokilavanianbazhagan@gmail.com>
wrote:
> Hi,
>
>
>
> We are using *DPDK-19.11.11* for our application in which 4 construction
> threads construct packets periodically, place it in a circular queue and
>
> a transmission thread pushes that packet by reading that circular queue.
>
>
> In the long run, We are facing a crash in *eth_igb_xmit_pkts() *call
> which is called during transmission.
>
>
> After an inspect with GDB, we came to know that the non-freed mbuf address
> is returned by* rte_pktmbuf_alloc() *for another packet during
> construction, even though that mbuf is still not transmitted by the
> transmission thread, which makes the corresponding construction thread to
> update the same memory again.
>
>
> It is not clear why rte_pktmbuf_alloc() returns the mbuf pointer before
> that pointer is not getting freed by rte_eth_tx_burst() call?.
>
>
> We have created the mempool using the call,
>
> *rte_pktmbuf_pool_create(txMemPoolName,
> 16384,RTE_MEMPOOL_CACHE_MAX_SIZE,0, 2048
> +RTE_PKTMBUF_HEADROOM, rte_eth_dev_socket_id(0));*
>
>
> Please guide us in resolving this issue.
>
>
>
> Thanks,
>
> Gokilavani A
>
>
>
[-- Attachment #2: Type: text/html, Size: 8995 bytes --]
next prev parent reply other threads:[~2022-10-25 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 11:09 Gokilavani A
2022-10-25 8:41 ` Gokilavani A [this message]
2022-10-27 17:34 ` Stephen Hemminger
2022-10-28 15:26 ` 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='CAFYD4LqCO7qo0Oa-HpMqqLS+Y94u8W69zn2O261us5y=c=5G6g@mail.gmail.com' \
--to=gokilavanianbazhagan@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).