DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: Ayuj Verma <ayverma@marvell.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
	Shally Verma <shallyv@marvell.com>,
	Sunila Sahu <ssahu@marvell.com>,
	"Kanaka Durga Kotamarthy" <kkotamarthy@marvell.com>,
	Arvind Desai <adesai@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] adding rsa priv key feature flag
Date: Wed, 13 Mar 2019 19:06:51 +0000	[thread overview]
Message-ID: <06EE24DD0B19E248B53F6DC8657831551B14AB4B@hasmsx109.ger.corp.intel.com> (raw)
In-Reply-To: <20190227133258.8962-1-ayverma@marvell.com>

V2 will be needed as test directory apparently changed its location.
Iam acking anyway.

> -----Original Message-----
> From: Ayuj Verma [mailto:ayverma@marvell.com]
> Sent: Wednesday, February 27, 2019 2:34 PM
> To: akhil.goyal@nxp.com
> Cc: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>; Shally Verma <shallyv@marvell.com>; Sunila Sahu
> <ssahu@marvell.com>; Kanaka Durga Kotamarthy
> <kkotamarthy@marvell.com>; Arvind Desai <adesai@marvell.com>;
> dev@dpdk.org; Ayuj Verma <ayverma@marvell.com>
> Subject: [PATCH v2 0/3] adding rsa priv key feature flag
> 
> Some PMDs can only support RSA private key operations using CRT
> (quintuple) or exponent key only. Thus it is required to add feature flag (ff) in
> PMD to reflect which key type is supported to perform sign and decrypt ops.
> 
> Thus add feature flags RTE_CRYPTODEV_FF_RSA_PRIV_OP_KEY_EXP
> and RTE_CRYPTODEV_FF_RSA_PRIV_OP_KEY_QT which would mean support
> to perform a private key op using CRT keys (quintuple) or exponent or both.
> 
> App should query PMD feature flag to check if specific key type is supported
> and call operation with relevant key type.
> 
> Ayuj Verma (3):
>   lib/cryptodev: add rsa priv key feature flag
>   crypto/openssl: set rsa private op feature flag
>   test/crypto: check for rsa key type feature flag
> 
>  drivers/crypto/openssl/rte_openssl_pmd.c |  4 +++-
>  lib/librte_cryptodev/rte_cryptodev.c     |  4 ++++
>  lib/librte_cryptodev/rte_cryptodev.h     |  4 ++++
>  test/test/test_cryptodev_asym.c          | 26 ++++++++++++++++++++++++
>  4 files changed, 37 insertions(+), 1 deletion(-)
> 
> --
> 2.20.0

Series-acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>

  parent reply	other threads:[~2019-03-13 19:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 13:33 Ayuj Verma
2019-02-27 13:33 ` [dpdk-dev] [PATCH v2 1/3] lib/cryptodev: add " Ayuj Verma
2019-03-17 17:46   ` Akhil Goyal
2019-03-17 17:46     ` Akhil Goyal
2019-03-18 18:05     ` Ayuj Verma
2019-03-18 18:05       ` Ayuj Verma
2019-02-27 13:33 ` [dpdk-dev] [PATCH v2 2/3] crypto/openssl: set rsa private op " Ayuj Verma
2019-02-27 13:33 ` [dpdk-dev] [PATCH v2 3/3] test/crypto: check for rsa key type " Ayuj Verma
2019-03-17 17:49   ` Akhil Goyal
2019-03-17 17:49     ` Akhil Goyal
2019-03-05  9:11 ` [dpdk-dev] [PATCH v2 0/3] adding rsa priv key " Ayuj Verma
2019-03-13  7:29   ` Ayuj Verma
2019-03-13 19:02     ` Kusztal, ArkadiuszX
2019-03-13 19:06 ` Kusztal, ArkadiuszX [this message]
2019-03-13 19:06   ` Kusztal, ArkadiuszX

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=06EE24DD0B19E248B53F6DC8657831551B14AB4B@hasmsx109.ger.corp.intel.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=adesai@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=ayverma@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=kkotamarthy@marvell.com \
    --cc=shallyv@marvell.com \
    --cc=ssahu@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).