From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] test/test: properly clean up on exit
Date: Fri, 5 Oct 2018 12:32:56 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A3B507D@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <e764e535-160b-5047-41ce-12dfb952b987@intel.com>
> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Friday, October 5, 2018 1:30 PM
> To: Pattan, Reshma <reshma.pattan@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] test/test: properly clean up on exit
>
> On 02-Aug-18 11:14 AM, Pattan, Reshma wrote:
> > Hi,
> >
> >> -----Original Message-----
> >> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anatoly Burakov
> >> Sent: Thursday, May 31, 2018 5:14 PM
> >> To: dev@dpdk.org
> >> Subject: [dpdk-dev] [PATCH] test/test: properly clean up on exit
> >>
> >> The test application didn't call rte_eal_cleanup() on exit, which
> >> caused leftover hugepages and memory leaks when running secondary
> >> processes. Fix this by calling rte_eal_cleanup() on exit.
> >>
> >> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> >> ---
> >> test/test/test.c | 33 +++++++++++++++++++++++----------
> >> 1 file changed, 23 insertions(+), 10 deletions(-)
> >
> > Reviewed-by: Reshma Pattan <reshma.pattan@intel.com>
> > Tested-by: Reshma Pattan <reshma.pattan@intel.com>
Acked-by: Reshma Pattan <reshma.pattan@intel.com>
next prev parent reply other threads:[~2018-10-05 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 16:14 Anatoly Burakov
2018-08-02 10:14 ` Pattan, Reshma
2018-10-05 12:29 ` Burakov, Anatoly
2018-10-05 12:32 ` Pattan, Reshma [this message]
2018-10-29 2:33 ` 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=3AEA2BF9852C6F48A459DA490692831F2A3B507D@irsmsx110.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@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).