From: Thomas Monjalon <thomas@monjalon.net>
To: Vipin Varghese <vipin.varghese@intel.com>
Cc: dev@dpdk.org, harry.van.haaren@intel.com, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] service: fix memory leak by rte_service_init
Date: Thu, 25 Jan 2018 23:10:57 +0100 [thread overview]
Message-ID: <1706116.QiZev3mjbx@xps> (raw)
In-Reply-To: <1515694853-7949-1-git-send-email-vipin.varghese@intel.com>
11/01/2018 19:20, Vipin Varghese:
> This patch fixes the memory leak created by rte_service_init. When
> secondary application which shares the huge page from primary, is
> executed multiple times memory is initialized but not freed on exit
>
> The rte_service_finalize checks if the service is initialized. If yes,
> it frees up rte_services & lcore_states. The API has to be called at
> end of application run.
>
> renamed the function from rte_service_deinit to rte_service_finalize.
This is a changelog. It should appear below ---
> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
Why not keeping previous ack?
Your patches have been set to "Not Applicable" in patchwork.
What happened?
next prev parent reply other threads:[~2018-01-25 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 14:46 [dpdk-dev] [PATCH v1] " Vipin Varghese
2018-01-08 10:17 ` Van Haaren, Harry
2018-01-08 14:40 ` Bruce Richardson
2018-01-11 18:20 ` [dpdk-dev] [PATCH v2] " Vipin Varghese
2018-01-25 22:10 ` Thomas Monjalon [this message]
2018-01-26 10:10 ` Van Haaren, Harry
2018-01-26 13:18 ` Thomas Monjalon
2018-01-26 20:55 ` [dpdk-dev] [PATCH v3] " Vipin Varghese
2018-01-26 15:20 ` Van Haaren, Harry
2018-01-26 16:54 ` 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=1706116.QiZev3mjbx@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--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).