* [dpdk-dev] is there any function like rte_mempool_destroy compare with rte_mempool_create
@ 2014-08-27 7:46 Ni, Xun
2014-08-27 8:14 ` Matthew Hall
0 siblings, 1 reply; 2+ messages in thread
From: Ni, Xun @ 2014-08-27 7:46 UTC (permalink / raw)
To: dev
Hello, folks:
I only see the rte_mempool_create but without function like rte_mempool_destroy? If I run an application twice, is there possible that the app has the memory leak? Or it just doesn't have enough memory to execute it again because the first one already get most of the memory but without release it.
Thanks,
Xun
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-dev] is there any function like rte_mempool_destroy compare with rte_mempool_create
2014-08-27 7:46 [dpdk-dev] is there any function like rte_mempool_destroy compare with rte_mempool_create Ni, Xun
@ 2014-08-27 8:14 ` Matthew Hall
0 siblings, 0 replies; 2+ messages in thread
From: Matthew Hall @ 2014-08-27 8:14 UTC (permalink / raw)
To: Ni, Xun; +Cc: dev
On Wed, Aug 27, 2014 at 07:46:26AM +0000, Ni, Xun wrote:
> If I run an application twice, is there possible that
> the app has the memory leak? Or it just doesn't have enough memory to
> execute it again because the first one already get most of the memory but
> without release it.
User-mapped memory should be freed by the kernel when the process dies.
However if there is multiprocess, shmem, or kernel resources being used in
your configuration anything could happen, including leaks.
Do you have some specifics about what you were doing / running?
Matthew.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-08-27 8:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-27 7:46 [dpdk-dev] is there any function like rte_mempool_destroy compare with rte_mempool_create Ni, Xun
2014-08-27 8:14 ` Matthew Hall
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).