From: Olivier Matz <olivier.matz@6wind.com>
To: Joyce Kong <joyce.kong@arm.com>
Cc: david.marchand@redhat.com, anatoly.burakov@intel.com,
andrew.rybchenko@oktetlabs.ru, yipeng1.wang@intel.com,
sameh.gobriel@intel.com, bruce.richardson@intel.com,
vladimir.medvedkin@intel.com, konstantin.ananyev@intel.com,
honnappa.nagarahalli@arm.com, ruifeng.wang@arm.com, dev@dpdk.org,
nd@arm.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] test/func_reentrancy: free memzones after creating test
Date: Thu, 16 Sep 2021 17:04:27 +0200 [thread overview]
Message-ID: <YUNc+2znC/lZUIN7@platinum> (raw)
In-Reply-To: <20210823025740.11828-1-joyce.kong@arm.com>
On Sun, Aug 22, 2021 at 09:57:40PM -0500, Joyce Kong wrote:
> Function reentrancy test limits maximum number of iterations
> simultaneously, however it doesn't free the 'fr_test_once'
> memzones after the fact, so introduce freeing 'fr_test_once'
> in ring/mempool/hash/fbk/lpm_clean.
>
> Meanwhile, add the missing free for test case on main thread.
>
> Fixes: 104a92bd026f ("app: add reentrancy tests")
> Fixes: 995eec619024 ("test: clean up memory for function reentrancy test")
> Cc: stable@dpdk.org
>
> Signed-off-by: Joyce Kong <joyce.kong@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Feifei Wang <feifei.wang2@arm.com>
Reviewed-by: Olivier Matz <olivier.matz@6wind.com>
next prev parent reply other threads:[~2021-09-16 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 7:33 [dpdk-dev] [PATCH v1] test/func_reentrancy: free memzones after creating test case Joyce Kong
2021-07-30 11:27 ` Olivier Matz
2021-07-31 8:42 ` Joyce Kong
2021-07-31 12:03 ` [dpdk-dev] [PATCH v2] " Joyce Kong
2021-08-17 8:17 ` David Marchand
2021-08-20 7:57 ` Joyce Kong
2021-08-20 8:52 ` David Marchand
2021-08-23 2:25 ` Joyce Kong
2021-08-20 8:12 ` [dpdk-dev] [PATCH v3] test/func_reentrancy: free memzones after creating test Joyce Kong
2021-08-23 2:57 ` [dpdk-dev] [PATCH v4] " Joyce Kong
2021-09-16 15:04 ` Olivier Matz [this message]
2021-09-16 15:09 ` David Marchand
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=YUNc+2znC/lZUIN7@platinum \
--to=olivier.matz@6wind.com \
--cc=anatoly.burakov@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=joyce.kong@arm.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.com \
--cc=sameh.gobriel@intel.com \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@intel.com \
--cc=yipeng1.wang@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).