From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5 0/4] Add PMD for asymmetric cryptography operations using Intel QuickAssist Technology devices
Date: Fri, 29 Mar 2019 14:27:19 +0000 [thread overview]
Message-ID: <dd1eac22-8bf2-6ec6-aa6d-a242dccde1ff@nxp.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435897211D3@IRSMSX101.ger.corp.intel.com>
On 3/28/2019 7:27 PM, Trahe, Fiona wrote:
>
>> -----Original Message-----
>> From: Kusztal, ArkadiuszX
>> Sent: Thursday, March 28, 2019 1:37 PM
>> To: dev@dpdk.org
>> Cc: akhil.goyal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>; Kusztal, ArkadiuszX
>> <arkadiuszx.kusztal@intel.com>
>> Subject: [PATCH v5 0/4] Add PMD for asymmetric cryptography operations using Intel QuickAssist
>> Technology devices
>>
>> This patchset adds Poll Mode Driver to use asymmetric cryptography
>> functions using Intel QuickAssist Techology devices.
>>
>> Following functions are available with this patchset:
>> * Modular Exponentiation
>> * Modular Inverse
>>
>> This patch depends on a QAT PF driver for device initialization. See
>> the file docs/guides/cryptodevs/qat.rst for configuration details.
>>
>> Limitations:
>> * Maximum parameter size: 4096 bits
>> - For both modular exponentiaion and modular multiplicative inverse
>>
>> v5:
>> - changed error checks order
>>
>> v4:
>> - fixed yet more checkpatch issues
>>
>> v3:
>> - fixed some checkpatch issues
>>
>> v2:
>> - added Meson build
>> - fixed segfault on cookie
>> - fixed mod inverse problem
>>
>> Arek Kusztal (4):
>> common/qat: add headers for asymmetric crypto
>> crypto/qat: add asymmetric cryptography PMD
>> crypto/qat: add modular exponentiation to qat asym pmd
>> crypto/qat: add modular inverse to qat asym pmd
> Series-acked-by: Fiona Trahe <fiona.trahe@intel.com>
>
Applied to dpdk-next-crypto
Thanks.
next prev parent reply other threads:[~2019-03-29 14:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 13:36 Arek Kusztal
2019-03-28 13:36 ` Arek Kusztal
2019-03-28 13:37 ` [dpdk-dev] [PATCH v5 1/4] common/qat: add headers for asymmetric crypto Arek Kusztal
2019-03-28 13:37 ` Arek Kusztal
2019-03-28 13:37 ` [dpdk-dev] [PATCH v5 2/4] crypto/qat: add asymmetric cryptography PMD Arek Kusztal
2019-03-28 13:37 ` Arek Kusztal
2019-04-03 8:42 ` Akhil Goyal
2019-04-03 8:42 ` Akhil Goyal
2019-04-03 9:05 ` Kusztal, ArkadiuszX
2019-04-03 9:05 ` Kusztal, ArkadiuszX
2019-03-28 13:37 ` [dpdk-dev] [PATCH v5 3/4] crypto/qat: add modular exponentiation to qat asym pmd Arek Kusztal
2019-03-28 13:37 ` Arek Kusztal
2019-03-28 13:37 ` [dpdk-dev] [PATCH v5 4/4] crypto/qat: add modular inverse " Arek Kusztal
2019-03-28 13:37 ` Arek Kusztal
2019-03-28 13:57 ` [dpdk-dev] [PATCH v5 0/4] Add PMD for asymmetric cryptography operations using Intel QuickAssist Technology devices Trahe, Fiona
2019-03-28 13:57 ` Trahe, Fiona
2019-03-29 14:27 ` Akhil Goyal [this message]
2019-03-29 14:27 ` 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=dd1eac22-8bf2-6ec6-aa6d-a242dccde1ff@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).