From: Stanislaw Kardach <kda@semihalf.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: Stanislaw Kardach <kda@semihalf.com>,
upstream@semihalf.com, dev@dpdk.org
Subject: [PATCH] test/ipsec: check for cryptodevs before testing
Date: Wed, 1 Jun 2022 13:00:17 +0200 [thread overview]
Message-ID: <20220601110017.400040-1-kda@semihalf.com> (raw)
Make sure that ipsec_perf_autotest checks if there are any crypto
devices available before it starts performance testing.
Same test is performed in the ipsec_autotest so it seems prudent to do
it here too to not introduce false failures.
Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
---
app/test/test_ipsec_perf.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/app/test/test_ipsec_perf.c b/app/test/test_ipsec_perf.c
index 346a851648..0eca003282 100644
--- a/app/test/test_ipsec_perf.c
+++ b/app/test/test_ipsec_perf.c
@@ -597,6 +597,12 @@ test_libipsec_perf(void)
uint32_t i;
int ret;
+ ret = rte_cryptodev_count();
+ if (ret < 1) {
+ RTE_LOG(WARNING, USER1, "No crypto devices found?\n");
+ return TEST_SKIPPED;
+ }
+
if (testsuite_setup() < 0) {
testsuite_teardown();
return TEST_FAILED;
--
2.30.2
next reply other threads:[~2022-06-01 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 11:00 Stanislaw Kardach [this message]
2022-06-21 13:10 ` [EXT] " 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=20220601110017.400040-1-kda@semihalf.com \
--to=kda@semihalf.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=upstream@semihalf.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).