From: David Coyle <david.coyle@intel.com>
To: akhil.goyal@nxp.com, declan.doherty@intel.com,
pablo.de.lara.guarch@intel.com, fiona.trahe@intel.com
Cc: dev@dpdk.org, brendan.ryan@intel.com,
mairtin.oloingsigh@intel.com, David Coyle <david.coyle@intel.com>
Subject: [dpdk-dev] [PATCH v1 2/2] app/crypto-perf: enable security feature for security tests
Date: Thu, 16 Jul 2020 16:29:52 +0100 [thread overview]
Message-ID: <20200716152952.65107-3-david.coyle@intel.com> (raw)
In-Reply-To: <20200716152952.65107-1-david.coyle@intel.com>
The RTE_CRYPTODEV_FF_SECURITY feature was disabled through the
ff_disable device configuration option for all crypto performance tests,
including security related tests. This patch updates the crypto
performance tool to not disable RTE_CRYPTODEV_FF_SECURITY for DOCSIS and
PDCP security tests.
Fixes: d4a131a9498d ("test/crypto-perf: support DOCSIS protocol")
Signed-off-by: David Coyle <david.coyle@intel.com>
---
app/test-crypto-perf/main.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/app/test-crypto-perf/main.c b/app/test-crypto-perf/main.c
index edeea9c1b..8f8e580e4 100644
--- a/app/test-crypto-perf/main.c
+++ b/app/test-crypto-perf/main.c
@@ -203,10 +203,13 @@ cperf_initialize_cryptodev(struct cperf_options *opts, uint8_t *enabled_cdevs)
struct rte_cryptodev_config conf = {
.nb_queue_pairs = opts->nb_qps,
.socket_id = socket_id,
- .ff_disable = RTE_CRYPTODEV_FF_SECURITY |
- RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO,
+ .ff_disable = RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO,
};
+ if (opts->op_type != CPERF_PDCP &&
+ opts->op_type != CPERF_DOCSIS)
+ conf.ff_disable |= RTE_CRYPTODEV_FF_SECURITY;
+
struct rte_cryptodev_qp_conf qp_conf = {
.nb_descriptors = opts->nb_descriptors
};
--
2.17.1
next prev parent reply other threads:[~2020-07-16 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 15:29 [dpdk-dev] [PATCH v1 0/2] " David Coyle
2020-07-16 15:29 ` [dpdk-dev] [PATCH v1 1/2] test/crypto: " David Coyle
2020-07-16 17:05 ` Akhil Goyal
2020-07-18 21:18 ` Akhil Goyal
2020-07-17 18:17 ` De Lara Guarch, Pablo
2020-07-18 20:07 ` Akhil Goyal
2020-07-16 15:29 ` David Coyle [this message]
2020-07-16 17:01 ` [dpdk-dev] [PATCH v1 2/2] app/crypto-perf: " Akhil Goyal
2020-07-17 18:19 ` De Lara Guarch, Pablo
2020-07-18 20:08 ` 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=20200716152952.65107-3-david.coyle@intel.com \
--to=david.coyle@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=brendan.ryan@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=mairtin.oloingsigh@intel.com \
--cc=pablo.de.lara.guarch@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).