From: Shally Verma <shallyv@marvell.com>
To: Anoob Joseph <anoobj@marvell.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Declan Doherty <declan.doherty@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Narayana Prasad Raju Athreya <pathreya@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/crypto-perf: disable asymmetric crypto
Date: Wed, 24 Jul 2019 09:31:15 +0000 [thread overview]
Message-ID: <BN6PR1801MB2052618EFEF4170A1A52F0A6ADC60@BN6PR1801MB2052.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1563959059-29754-1-git-send-email-anoobj@marvell.com>
> -----Original Message-----
> From: Anoob Joseph <anoobj@marvell.com>
> Sent: Wednesday, July 24, 2019 2:34 PM
> To: Akhil Goyal <akhil.goyal@nxp.com>; Declan Doherty
> <declan.doherty@intel.com>; Pablo de Lara
> <pablo.de.lara.guarch@intel.com>
> Cc: Anoob Joseph <anoobj@marvell.com>; Jerin Jacob Kollanukkaran
> <jerinj@marvell.com>; Narayana Prasad Raju Athreya
> <pathreya@marvell.com>; Shally Verma <shallyv@marvell.com>;
> dev@dpdk.org
> Subject: [PATCH] app/crypto-perf: disable asymmetric crypto
>
> Asymmetric crypto is not required for test-crypto-perf application.
> Disabling the feature using 'ff_disable' field.
>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> ---
Acked-by: Shally Verma <shallyv@marvell.com>
> app/test-crypto-perf/main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/app/test-crypto-perf/main.c b/app/test-crypto-perf/main.c index
> ce92a96..2109e70 100644
> --- a/app/test-crypto-perf/main.c
> +++ b/app/test-crypto-perf/main.c
> @@ -201,7 +201,8 @@ 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,
> + .ff_disable = RTE_CRYPTODEV_FF_SECURITY |
> +
> RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO,
> };
>
> struct rte_cryptodev_qp_conf qp_conf = {
> --
> 2.7.4
next prev parent reply other threads:[~2019-07-24 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 9:04 Anoob Joseph
2019-07-24 9:31 ` Shally Verma [this message]
2019-07-24 16:21 ` Trahe, Fiona
2019-07-26 12:42 ` 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=BN6PR1801MB2052618EFEF4170A1A52F0A6ADC60@BN6PR1801MB2052.namprd18.prod.outlook.com \
--to=shallyv@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pathreya@marvell.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).