From: Akhil Goyal <akhil.goyal@nxp.com>
To: Shally Verma <shallyv@marvell.com>,
Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "fiona.trahe@intel.com" <fiona.trahe@intel.com>,
"shally.verma@caviumnetworks.com"
<shally.verma@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/3] cryptodev: add result field to mod exp and inverse operations
Date: Thu, 28 Feb 2019 09:59:23 +0000 [thread overview]
Message-ID: <fcfb0704-38d2-4080-5dc6-c5f622af11ba@nxp.com> (raw)
In-Reply-To: <CY4PR1801MB205307FC8EAF36BE25F5B00EAD650@CY4PR1801MB2053.namprd18.prod.outlook.com>
On 2/12/2019 4:25 PM, Shally Verma wrote:
>
>> -----Original Message-----
>> From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>> Sent: 08 February 2019 16:44
>> To: dev@dpdk.org
>> Cc: akhil.goyal@nxp.com; fiona.trahe@intel.com; shally.verma@caviumnetworks.com; Arek Kusztal <arkadiuszx.kusztal@intel.com>
>> Subject: [PATCH v2 1/3] cryptodev: add result field to mod exp and inverse operations
>>
>> External Email
>>
>> This commit adds result field to be used when modular exponentiation or
>> modular multiplicative inverse operation is used
>>
>> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>> ---
> Acked-by: Shally Verma <shallyv@marvell.com>
>
>> lib/librte_cryptodev/rte_crypto_asym.h | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/lib/librte_cryptodev/rte_crypto_asym.h b/lib/librte_cryptodev/rte_crypto_asym.h
>> index 0a50cd5..991263f 100644
>> --- a/lib/librte_cryptodev/rte_crypto_asym.h
>> +++ b/lib/librte_cryptodev/rte_crypto_asym.h
>> @@ -339,6 +339,16 @@ struct rte_crypto_mod_op_param {
>> * be relatively prime to modulus in corresponding Modular
>> * Multiplicative Inverse rte_crypto_modinv_xform
>> */
>> +
>> + rte_crypto_param result;
ABI breakage??
Do we have a deprecation notice?
>> + /**<
>> + * Pointer to the result of modular exponentiation/multiplicative inverse
>> + * data in octet-string network byte order format.
>> + *
>> + * This field shall be big enough to hold the result of Modular
>> + * Exponentiation or Modular Multplicative Inverse
>> + * (bigger or equal to length of modulus)
>> + */
>> };
>>
>> /**
>> --
>> 2.1.0
next prev parent reply other threads:[~2019-02-28 9:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 11:13 [dpdk-dev] [PATCH v2 0/3] crypotodev: add result field to modular operations Arek Kusztal
2019-02-08 11:13 ` [dpdk-dev] [PATCH v2 1/3] cryptodev: add result field to mod exp and inverse operations Arek Kusztal
2019-02-12 10:55 ` Shally Verma
2019-02-28 9:59 ` Akhil Goyal [this message]
2019-02-28 10:44 ` Kusztal, ArkadiuszX
2019-02-28 10:52 ` Akhil Goyal
2019-02-08 11:13 ` [dpdk-dev] [PATCH v2 2/3] openssl: add result field to mod exp and mod inv operations Arek Kusztal
2019-02-08 11:13 ` [dpdk-dev] [PATCH v2 3/3] test: add result field to mod exp and mod inv Arek Kusztal
2019-02-12 11:00 ` Shally Verma
2019-02-08 12:31 ` [dpdk-dev] [PATCH v2 0/3] crypotodev: add result field to modular operations Trahe, Fiona
2019-03-19 14:02 ` Akhil Goyal
2019-03-19 14:02 ` 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=fcfb0704-38d2-4080-5dc6-c5f622af11ba@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=shally.verma@caviumnetworks.com \
--cc=shallyv@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).