From: Thomas Monjalon <thomas@monjalon.net>
To: Phil Yang <phil.yang@arm.com>
Cc: dev@dpdk.org, nd@arm.com, gavin.hu@arm.com
Subject: Re: [dpdk-dev] [PATCH 1/2] test/pmd_ring_perf: release ring resources after test
Date: Sun, 18 Nov 2018 23:21:07 +0100 [thread overview]
Message-ID: <12856267.c78D8TC06a@xps> (raw)
In-Reply-To: <1539946839-12996-1-git-send-email-phil.yang@arm.com>
19/10/2018 13:00, Phil Yang:
> Need to release the port and the ring resources after test. Otherwise,
> it will cause failure to allocate memory when reentry the test.
>
> Fixes: ea764af ("app/test: add performance test for ring driver")
>
> Signed-off-by: Phil Yang <phil.yang@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
This patch was out of the radar because patch 2 was superseded.
Applied, thanks
next prev parent reply other threads:[~2018-11-18 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 11:00 Phil Yang
2018-10-19 11:00 ` [dpdk-dev] [PATCH 2/2] test/pmd_ring: " Phil Yang
2018-10-19 11:12 ` [dpdk-dev] [PATCH v2] " Phil Yang
2018-10-30 0:42 ` Phil Yang (Arm Technology China)
2018-11-18 22:21 ` Thomas Monjalon [this message]
2018-11-19 1:42 ` [dpdk-dev] [PATCH 1/2] test/pmd_ring_perf: " Phil Yang (Arm Technology China)
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=12856267.c78D8TC06a@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=nd@arm.com \
--cc=phil.yang@arm.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).