DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ray Kinsella <mdr@ashroe.eu>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Subject: Re: [EXT] [PATCH v5 06/12] cryptodev: add elliptic curve diffie hellman
Date: Thu, 02 Jun 2022 15:21:16 +0100	[thread overview]
Message-ID: <87y1yfp2mw.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <CO6PR18MB4484707E856CDAD002B86D9CD8DE9@CO6PR18MB4484.namprd18.prod.outlook.com>


Akhil Goyal <gakhil@marvell.com> writes:

>> - Added elliptic curve Diffie-Hellman parameters.
>> Point multiplication allows the user to process every phase of
>> ECDH, but for phase 1, user should not really care about the generator.
>> The user does not even need to know what the generator looks like,
>> therefore setting ec xform would make this work.
>> 
>> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>> ---
>>  devtools/libabigail.abignore               |  3 +++
>>  doc/guides/cryptodevs/features/default.ini |  1 +
>>  doc/guides/prog_guide/cryptodev_lib.rst    |  7 +++---
>>  doc/guides/rel_notes/release_22_07.rst     |  2 ++
>>  lib/cryptodev/rte_crypto_asym.h            | 38
>> ++++++++++++++++++++++++++++++
>>  5 files changed, 48 insertions(+), 3 deletions(-)
>> 
>> diff --git a/devtools/libabigail.abignore b/devtools/libabigail.abignore
>> index 79ff15dc4e..6d174b291f 100644
>> --- a/devtools/libabigail.abignore
>> +++ b/devtools/libabigail.abignore
>> @@ -27,6 +27,9 @@
>>  ; Ignore changes to rte_crypto_asym_op, asymmetric crypto API is
>> experimental
>>  [suppress_type]
>>          name = rte_crypto_asym_op
>> +; Ignore changes to rte_crypto_asym_xform_type, asymmetric crypto API is
>> experimental
>> +[suppress_type]
>> +        name = rte_crypto_asym_xform_type
>> 
> This exception does not seem to work.
> Thomas and I are getting ABI issues even with this suppress rule.
>
>   [C] 'function void rte_cryptodev_info_get(uint8_t, rte_cryptodev_info*)' at rte_cryptodev.c:1582:1 has some indirect sub-type changes:
>     parameter 2 of type 'rte_cryptodev_info*' has sub-type changes:
>       in pointed to type 'struct rte_cryptodev_info' at rte_cryptodev.h:503:1:
>         type size hasn't changed
>         1 data member change:
>           type of 'const rte_cryptodev_capabilities* capabilities' changed:
>             in pointed to type 'const rte_cryptodev_capabilities':
>               in unqualified underlying type 'struct rte_cryptodev_capabilities' at rte_cryptodev.h:198:1:
>                 type size hasn't changed
>                 1 data member change:
>                   type of 'anonymous data member union {rte_cryptodev_symmetric_capability sym; rte_cryptodev_asymmetric_capability asym;}' changed:
>                     type size hasn't changed
>                     1 data member change:
>                       type of 'rte_cryptodev_asymmetric_capability asym' changed:
>                         type size hasn't changed
>                         1 data member change:
>                           type of 'rte_cryptodev_asymmetric_xform_capability xform_capa' changed:
>                             type size hasn't changed
>                             1 data member change:
>                               type of 'rte_crypto_asym_xform_type xform_type' changed:
>                                 type size hasn't changed
>                                 1 enumerator insertion:
>                                   'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_ECDH' value '8'
>                                 2 enumerator changes:
>                                   'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_ECPM' from value '8' to '9' at rte_crypto_asym.h:80:1
>                                   'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END' from value '9' to '10' at rte_crypto_asym.h:80:1

Ok - will take a look see.

-- 
Regards, Ray K

  reply	other threads:[~2022-06-02 14:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01  9:02 [PATCH v5 00/12] cryptodev: rsa, dh, ecdh changes Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 01/12] cryptodev: redefine ec group enum Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 02/12] cryptodev: separate key exchange operation enum Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 03/12] cryptodev: remove comment about using ephemeral key in dsa Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 04/12] cryptodev: clarify usage of private key in dh Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 05/12] cryptodev: move dh type from xform to dh op Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 06/12] cryptodev: add elliptic curve diffie hellman Arek Kusztal
2022-06-01 10:14   ` Kusztal, ArkadiuszX
2022-06-02 13:33   ` [EXT] " Akhil Goyal
2022-06-02 14:21     ` Ray Kinsella [this message]
2022-06-02 14:25       ` Akhil Goyal
2022-06-02 14:46         ` Kusztal, ArkadiuszX
2022-06-03 13:26           ` Ray Kinsella
2022-06-01  9:02 ` [PATCH v5 07/12] cryptodev: add public key verify option Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 08/12] cryptodev: add asym op flags Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 09/12] cryptodev: clarify usage of rsa padding hash Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 10/12] cryptodev: move RSA padding into separate struct Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 11/12] cryptodev: clarify rsa verify with none padding Arek Kusztal
2022-06-01  9:02 ` [PATCH v5 12/12] cryptodev: add salt length and optional label Arek Kusztal
2022-06-02 10:07 ` [EXT] [PATCH v5 00/12] cryptodev: rsa, dh, ecdh changes 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=87y1yfp2mw.fsf@mdr78.vserver.site \
    --to=mdr@ashroe.eu \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=roy.fan.zhang@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).