From: svaralak <varalakshmi.s@intel.com>
To: dts@dpdk.org
Cc: varalakshmi.s@intel.com
Subject: [PATCH V2] tests/TestSuite_ipsec_gw_cryptodev_func.py tests/TestSuite_crypto_perf_cryptodev_perf.py: Modified to accomodate qat_legacy_capa flag
Date: Fri, 22 Sep 2023 17:18:54 +0800 [thread overview]
Message-ID: <20230922091854.100135-1-varalakshmi.s@intel.com> (raw)
Fix the script to include qat_legacy_capa flag with QAT devices.
Signed-off-by: svaralak <varalakshmi.s@intel.com>
---
tests/TestSuite_crypto_perf_cryptodev_perf.py | 13 ++++++++++++-
tests/TestSuite_ipsec_gw_cryptodev_func.py | 5 +++++
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/tests/TestSuite_crypto_perf_cryptodev_perf.py b/tests/TestSuite_crypto_perf_cryptodev_perf.py
index 0531b9c6..7c4f8de6 100644
--- a/tests/TestSuite_crypto_perf_cryptodev_perf.py
+++ b/tests/TestSuite_crypto_perf_cryptodev_perf.py
@@ -349,6 +349,11 @@ class TestCryptoPerfCryptodevPerf(TestCase):
dev = "crypto_aesni_mb"
elif self.get_case_cfg()["devtype"] == "crypto_qat":
w = cc.get_qat_devices(self, cpm_num=1, num=num)
+ legacy_capa_flag=",qat_legacy_capa=1"
+ i = 0
+ for s in w:
+ w[i] = s+legacy_capa_flag
+ i = i + 1
device["a"] = " -a ".join(w)
device["vdev"] = None
elif self.get_case_cfg()["devtype"] == "crypto_openssl":
@@ -364,6 +369,7 @@ class TestCryptoPerfCryptodevPerf(TestCase):
elif self.get_case_cfg()["devtype"] == "crypto_scheduler":
dev = "crypto_scheduler"
w = cc.get_qat_devices(self, cpm_num=3, num=num * 3)
+
if not w:
return {}
vdev_list = []
@@ -371,7 +377,12 @@ class TestCryptoPerfCryptodevPerf(TestCase):
vdev = "{}{},worker={}_qat_sym,worker={}_qat_sym,worker={}_qat_sym,mode=round-robin".format(
dev, i, w[i * 3], w[i * 3 + 1], w[i * 3 + 2]
)
- vdev_list.append(vdev)
+ vdev_list.append(vdev)
+ legacy_capa_flag=",qat_legacy_capa=1"
+ i = 0
+ for s in w:
+ w[i] = s+legacy_capa_flag
+ i = i + 1
device["a"] = " -a ".join(w)
device["vdev"] = " --vdev ".join(vdev_list)
else:
diff --git a/tests/TestSuite_ipsec_gw_cryptodev_func.py b/tests/TestSuite_ipsec_gw_cryptodev_func.py
index d9f6f626..fe4222d5 100644
--- a/tests/TestSuite_ipsec_gw_cryptodev_func.py
+++ b/tests/TestSuite_ipsec_gw_cryptodev_func.py
@@ -225,6 +225,11 @@ class TestIPsecGwCryptodevFunc(TestCase):
dev = "crypto_aesni_mb"
elif self.get_case_cfg()["devtype"] == "crypto_qat":
w = cc.get_qat_devices(self, cpm_num=1, num=num)
+ legacy_capa_flag=",qat_legacy_capa=1"
+ i = 0
+ for s in w:
+ w[i] = s+legacy_capa_flag
+ i = i + 1
device["a"] = " -a ".join(w)
device["vdev"] = None
elif self.get_case_cfg()["devtype"] == "crypto_openssl":
--
2.17.1
reply other threads:[~2023-09-22 8:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230922091854.100135-1-varalakshmi.s@intel.com \
--to=varalakshmi.s@intel.com \
--cc=dts@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).