From: Matthew Hall <mhall@mhcomputing.net>
To: "Ni, Xun" <xun.ni@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] is there any function like rte_mempool_destroy compare with rte_mempool_create
Date: Wed, 27 Aug 2014 01:14:59 -0700 [thread overview]
Message-ID: <20140827081459.GA8217@mhcomputing.net> (raw)
In-Reply-To: <91E2D863603AD4478F101CE81E76E45D01B5DFE8@SHSMSX103.ccr.corp.intel.com>
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.
prev parent reply other threads:[~2014-08-27 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 7:46 Ni, Xun
2014-08-27 8:14 ` Matthew Hall [this message]
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=20140827081459.GA8217@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=xun.ni@intel.com \
/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).