From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Shally Verma <shally.verma@caviumnetworks.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "Doherty, Declan" <declan.doherty@intel.com>,
"pathreya@caviumnetworks.com" <pathreya@caviumnetworks.com>,
"ssahu@caviumnetworks.com" <ssahu@caviumnetworks.com>,
"agupta@caviumnetworks.com" <agupta@caviumnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Sunila Sahu <sunila.sahu@caviumnetworks.com>,
Ashish Gupta <ashish.gupta@caviumnetworks.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [PATCH v2 5/6] crypto/openssl: add asym crypto support
Date: Wed, 9 May 2018 10:33:01 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B4358947D9A6@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1522927489-23668-6-git-send-email-shally.verma@caviumnetworks.com>
Hi Shally,
> -----Original Message-----
> From: Shally Verma [mailto:shally.verma@caviumnetworks.com]
> Sent: Thursday, April 5, 2018 12:25 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: Doherty, Declan <declan.doherty@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>;
> pathreya@caviumnetworks.com; ssahu@caviumnetworks.com; agupta@caviumnetworks.com;
> dev@dpdk.org; Sunila Sahu <sunila.sahu@caviumnetworks.com>; Ashish Gupta
> <ashish.gupta@caviumnetworks.com>
> Subject: [PATCH v2 5/6] crypto/openssl: add asym crypto support
>
> Add asymmetric crypto operation support in openssl PMD.
> Current list of supported asym xforms:
> * RSA
> * DSA
> * Deffie-hellman
> * Modular Operations
[Fiona] What was your rationale for adding this into the openssl PMD vs creating a new openssl_asym PMD?
Will this work ok if there's a burst of ops including asym and sym operations enqueued to the same qp?
next prev parent reply other threads:[~2018-05-09 10:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 11:24 [PATCH v2 0/6] crypto: add asym crypto support Shally Verma
2018-04-05 11:24 ` [PATCH v2 1/6] lib/cryptodev: add asymmetric algos in cryptodev Shally Verma
2018-05-08 15:08 ` Trahe, Fiona
2018-04-05 11:24 ` [PATCH v2 2/6] lib/cryptodev: add asym op support " Shally Verma
2018-05-08 10:51 ` Trahe, Fiona
2018-05-08 10:58 ` Verma, Shally
2018-05-08 18:32 ` De Lara Guarch, Pablo
2018-05-08 14:43 ` Trahe, Fiona
2018-05-09 7:33 ` Verma, Shally
2018-04-05 11:24 ` [PATCH v2 3/6] lib/cryptodev: add asymmetric crypto capability " Shally Verma
2018-05-08 15:00 ` Trahe, Fiona
2018-05-09 7:34 ` Verma, Shally
2018-04-05 11:24 ` [PATCH v2 4/6] test/crypto: add unit testcase for asym crypto Shally Verma
2018-04-05 11:24 ` [PATCH v2 5/6] crypto/openssl: add asym crypto support Shally Verma
2018-05-09 10:33 ` Trahe, Fiona [this message]
2018-05-09 10:56 ` Verma, Shally
2018-04-05 11:24 ` [PATCH v2 6/6] doc: add asym crypto in cryptodev programmer guide Shally Verma
2018-04-11 12:37 ` [PATCH v2 0/6] crypto: add asym crypto support De Lara Guarch, Pablo
2018-04-11 14:14 ` Verma, Shally
2018-04-20 6:16 ` Verma, Shally
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=348A99DA5F5B7549AA880327E580B4358947D9A6@IRSMSX103.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=agupta@caviumnetworks.com \
--cc=ashish.gupta@caviumnetworks.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pathreya@caviumnetworks.com \
--cc=shally.verma@caviumnetworks.com \
--cc=ssahu@caviumnetworks.com \
--cc=sunila.sahu@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.