From: "Ji, Kai" <kai.ji@intel.com>
To: dpdk stable <stable@dpdk.org>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Jiang, YuX" <yux.jiang@intel.com>,
"ktraynor@redhat.com" <ktraynor@redhat.com>
Subject: FW: [PATCH 21.11.1 v2] test/crypto: skip oop test for raw api
Date: Tue, 16 Aug 2022 14:43:34 +0000 [thread overview]
Message-ID: <SN6PR11MB340833A2684996F8A13CE8FE816B9@SN6PR11MB3408.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB34085D01DE954E295442DE5081959@SN6PR11MB3408.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
> -----Original Message-----
> From: Ji, Kai
> Sent: Monday, July 25, 2022 12:44 PM
> To: ktraynor@redhat.com
> Cc: hemant.agrawal@nxp.com; Poczatek, Jakub
> <jakub.poczatek@intel.com>; Jiang, YuX <YuX.Jiang@intel.com>
> Subject: [PATCH 21.11.1 v2] test/crypto: skip oop test for raw api
>
> Hi Kevin,
>
> The attached patch fix a single failing oop test in raw api where it supposed to
> be skipped, and this test also failed in next-crypto 21.11 release.
> Because of major qat data-path refactor has been included in next-crypto
> 22.03 release, this test is passing now as the OOP feature is supported by
> refactor.
>
> So I didn't include upstream commit id in this patch as I'm not sure the fix will
> be needed for the next-crypto anymore.
>
> Can you check to see if this patch is qualified to be merged into LTS 21.11.1 v2?
>
> Regards
>
> Kai
>
[-- Attachment #2: v1-0001-test-crypto-skip-oop-test-for-raw-api.patch --]
[-- Type: application/octet-stream, Size: 1372 bytes --]
From f0046f0429098e668a4d2ffa5a80bce91f8c1635 Mon Sep 17 00:00:00 2001
From: Kai Ji <kai.ji@intel.com>
Date: Thu, 14 Apr 2022 01:59:43 +0800
Subject: [PATCH 21.11.1 v2 v1 1/1] test/crypto: skip oop test for raw api
Add in api test type check to skip unsupported aead OOP testcase
in raw API test.
Fixes: cd8166c28cd1 ("test/crypto: add raw API test for dpaax")
Cc: hemant.agrawal@nxp.com
Signed-off-by: Kai Ji <kai.ji@intel.com>
Tested-by: Poczatek, Jakub <jakub.poczatek@intel.com>
---
app/test/test_cryptodev.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
index 41a8b10a90..b11be735d0 100644
--- a/app/test/test_cryptodev.c
+++ b/app/test/test_cryptodev.c
@@ -10547,9 +10547,11 @@ test_authenticated_encryption_oop(const struct aead_test_data *tdata)
rte_cryptodev_info_get(ts_params->valid_devs[0], &dev_info);
uint64_t feat_flags = dev_info.feature_flags;
- if ((global_api_test_type == CRYPTODEV_RAW_API_TEST) &&
- (!(feat_flags & RTE_CRYPTODEV_FF_SYM_RAW_DP)))
+ if ((global_api_test_type == CRYPTODEV_RAW_API_TEST) ||
+ (!(feat_flags & RTE_CRYPTODEV_FF_SYM_RAW_DP))) {
+ printf("Device does not support RAW data-path APIs.\n");
return TEST_SKIPPED;
+ }
/* not supported with CPU crypto */
if (gbl_action_type == RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO)
--
2.17.1
next parent reply other threads:[~2022-08-16 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SN6PR11MB34085D01DE954E295442DE5081959@SN6PR11MB3408.namprd11.prod.outlook.com>
2022-08-16 14:43 ` Ji, Kai [this message]
2022-08-17 9:26 ` Luca Boccassi
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=SN6PR11MB340833A2684996F8A13CE8FE816B9@SN6PR11MB3408.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--cc=yux.jiang@intel.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).