From: Adam Dybkowski <adamx.dybkowski@intel.com>
To: dev@dpdk.org, declan.doherty@intel.com, arkadiuszx.kusztal@intel.com
Cc: Adam Dybkowski <adamx.dybkowski@intel.com>
Subject: [dpdk-dev] [PATCH 1/2] test/crypto: close PMD after tests
Date: Mon, 1 Mar 2021 12:21:09 +0000 [thread overview]
Message-ID: <20210301122110.2586-1-adamx.dybkowski@intel.com> (raw)
This patch adds closing of the PMD after running the tests.
Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
---
app/test/test_cryptodev.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
index f91debc16..7dcd255de 100644
--- a/app/test/test_cryptodev.c
+++ b/app/test/test_cryptodev.c
@@ -976,8 +976,9 @@ ut_teardown(void)
rte_cryptodev_stats_get(ts_params->valid_devs[0], &stats);
- /* Stop the device */
+ /* Stop and close the device */
rte_cryptodev_stop(ts_params->valid_devs[0]);
+ rte_cryptodev_close(ts_params->valid_devs[0]);
}
static int
--
2.25.1
next reply other threads:[~2021-03-01 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 12:21 Adam Dybkowski [this message]
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 ` [dpdk-dev] [PATCH v3 " Adam Dybkowski
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=20210301122110.2586-1-adamx.dybkowski@intel.com \
--to=adamx.dybkowski@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=declan.doherty@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).