From: 宋捷 <songj@zctt.com>
To: <users@dpdk.org>, "'Van Haaren, Harry'" <harry.van.haaren@intel.com>
Subject: [dpdk-users] How to free a rte_mempool buffer
Date: Thu, 21 Mar 2019 16:48:08 +0800 [thread overview]
Message-ID: <000901d4dfc2$cee23e10$6ca6ba30$@zctt.com> (raw)
Hi All,
I test my DPDK program in VM Ubuntu (in VMware) with the two virtual
NICs(VMXNET3 and e1000).
I create a rte_mempool buffer by rte_pktmbuf_pool_create, and load some
packets from a pcap file into this buffer. I can sending these packets by
rte_eth_tx_burst successfully.
Now I want to load another pcap file, then I free the previous rte_mempool
buffer by rte_mempool_free, and create a new rte_mempool buffer,
But a crash will be occurred at rte_eth_tx_burst Both in VMXNET3 and e1000.
I traced the code and found the crash point as below:
The VMXNET3 driver: crash at:
vmxnet3_xmit_pkts->vmxnet3_tq_tx_complete->vmxnet3_unmap_pkt->rte_pktmbuf_fr
ee(mbuf); (mbuf = txq->cmd_ring.buf_info[eop_idx].m;)
The e1000 driver: crash at:
eth_em_xmit_pkts->rte_pktmbuf_free_seg(txe->mbuf);
I think rte_mempool_free side effects the driver’s TX ring, but don’t know
how to fix this issue?
How can we free a rte_mempool buffer safely?
Thanks
Jie
next reply other threads:[~2019-03-21 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 8:48 宋捷 [this message]
2019-03-21 10:51 ` Van Haaren, Harry
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='000901d4dfc2$cee23e10$6ca6ba30$@zctt.com' \
--to=songj@zctt.com \
--cc=harry.van.haaren@intel.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).