From: Thomas Monjalon <thomas@monjalon.net>
To: Vipin Varghese <vipin.varghese@intel.com>, harry.van.haaren@intel.com
Cc: stable@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2] app/procinfo: Fix memory leak by rte_service_init
Date: Fri, 26 Jan 2018 17:59:47 +0100 [thread overview]
Message-ID: <1543040.UXSxQDX3pr@xps> (raw)
In-Reply-To: <1515700054-29654-1-git-send-email-vipin.varghese@intel.com>
11/01/2018 20:47, Vipin Varghese:
> When procinfo is run multiple times against primary application, it
> consumes huge page memory by rte_service_init. Which is not released
> at exit of application.
>
> Invoking rte_service_finalize to real memory and prevent memory leak.
I don't think it is correct to call rte_service_finalize in applications,
while rte_service_init is called in EAL.
Maybe we need a new function in EAL.
next prev parent reply other threads:[~2018-01-26 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1514735641-8738-1-git-send-email-vipin.varghese@intel.com>
2018-01-11 19:47 ` Vipin Varghese
2018-01-26 15:44 ` Van Haaren, Harry
2018-01-26 16:59 ` Thomas Monjalon [this message]
2018-01-26 17:15 ` Van Haaren, Harry
2018-01-26 17:26 ` Thomas Monjalon
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=1543040.UXSxQDX3pr@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=stable@dpdk.org \
--cc=vipin.varghese@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).