From: Adam Dybkowski <adamx.dybkowski@intel.com>
To: dev@dpdk.org, declan.doherty@intel.com,
arkadiuszx.kusztal@intel.com, gakhil@marvell.com
Cc: Adam Dybkowski <adamx.dybkowski@intel.com>
Subject: [dpdk-dev] [PATCH v3 0/2] test/crypto: close PMD after tests
Date: Fri, 9 Apr 2021 13:12:59 +0100 [thread overview]
Message-ID: <20210409121301.57789-1-adamx.dybkowski@intel.com> (raw)
In-Reply-To: <20210308125708.31525-1-adamx.dybkowski@intel.com>
This patch adds closing of the PMD after running the tests.
--
v3:
* move the call from ut_teardown to testsuite_teardown
v2:
* display error message on close error
Adam Dybkowski (2):
test/crypto: close PMD after tests
app/crypto-perf: close PMD after benchmark run
app/test-crypto-perf/main.c | 15 +++++++++++++--
app/test/test_cryptodev.c | 5 +++++
2 files changed, 18 insertions(+), 2 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2021-04-09 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 12:21 [dpdk-dev] [PATCH 1/2] " Adam Dybkowski
2021-03-01 12:21 ` [dpdk-dev] [PATCH 2/2] app/crypto-perf: close PMD after benchmark run Adam Dybkowski
2021-03-08 12:57 ` [dpdk-dev] [PATCH v2 0/2] test/crypto: close PMD after tests Adam Dybkowski
2021-03-08 12:57 ` [dpdk-dev] [PATCH v2 1/2] " Adam Dybkowski
2021-03-08 12:57 ` [dpdk-dev] [PATCH v2 2/2] app/crypto-perf: close PMD after benchmark run Adam Dybkowski
2021-03-08 13:45 ` [dpdk-dev] [PATCH v2 0/2] test/crypto: close PMD after tests Kusztal, ArkadiuszX
2021-04-09 12:12 ` Adam Dybkowski [this message]
2021-04-09 12:13 ` [dpdk-dev] [PATCH v3 1/2] " Adam Dybkowski
2021-04-09 12:13 ` [dpdk-dev] [PATCH v3 2/2] app/crypto-perf: close PMD after benchmark run Adam Dybkowski
2021-04-13 13:33 ` [dpdk-dev] [EXT] [PATCH v3 0/2] test/crypto: close PMD after tests Akhil Goyal
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=20210409121301.57789-1-adamx.dybkowski@intel.com \
--to=adamx.dybkowski@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.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).