From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D0990A055F; Fri, 27 May 2022 09:27:52 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BCC0040E5A; Fri, 27 May 2022 09:27:52 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) by mails.dpdk.org (Postfix) with ESMTP id 76B5740E50 for ; Fri, 27 May 2022 09:27:51 +0200 (CEST) Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 24R7Ph00024879; Fri, 27 May 2022 00:27:50 -0700 Received: from nam10-dm6-obe.outbound.protection.outlook.com (mail-dm6nam10lp2101.outbound.protection.outlook.com [104.47.58.101]) by mx0b-0016f401.pphosted.com (PPS) with ESMTPS id 3g93tyckun-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 27 May 2022 00:27:50 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PTSgYFWp6t36Gc+CichbJClcBme+OwHTV31tNd/Onk2CWyAOHLQSeUd217b9BPiY+/UHp4CtuojugMm/yaPZY6ldCmE2sWog1/xYghKoece4Du9fHIfS7JFGzw12oNYYdwzpU6fkawOleZizX3fogXehAkFBoZFE0YlDy3YKRo/ttXZ3FdkxI8glsgZ8PwCk84fQG3ws1RJzKDEQgn4ryUA27MYFAYycKWZFgEoclp0hYmF5xxsdQOfGNeKmfa0sG1VgXSocOIzS8SYgZlI0uAwU5bKLsHcOQaMO0wtubarHBtNS8tiYnvjMS+4KuTDRjH65RJGwtwY7jkUzNPDqjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=O5lXstmIEr9Z7+Ck9pcuhU2kxHUpelSEJfxTn8eCF18=; b=JlAbvMCWWLhilThrjHtif8EJ7M5Lrb3A+I6vcJ25x+r1LMbV6qJefgxqbGqZH2v243EFo8VIWDgmROjRnEL51pFL+PNODJuUA6QPlGV2o13NT9XGbbPbU6eprYB/7uGNR2itxEKiLX/bEOSfKFW2mrSzpkLhNmXVC8VzOHzwzIzUZ1UMNa1ucnURmLCcQ2UELsRE+hey3/Qh768QBu4vYdEw4DA6Ncjn+RIiFo21i/8zqlnvv+8Kgw+1HL7h8esYaFcnGAIcu2M/B3SBceyynaWUSZjJWUPeMJMnXfKivwUIR2dCq23QzLrlZQ5VXxV9vlx4ICYBTSC92x96u5Mfcw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=marvell.com; dmarc=pass action=none header.from=marvell.com; dkim=pass header.d=marvell.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.onmicrosoft.com; s=selector1-marvell-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=O5lXstmIEr9Z7+Ck9pcuhU2kxHUpelSEJfxTn8eCF18=; b=FonD8dHuZ8ZDi8gxjSYayCF5p6P+WwX4RTlJPE2gu5eQr3NFpnkitb89syA3zEbAJXA8W9widFbhnnh8EK1oECl9pusFjkrLijunN8M434aS5Y/Hmzgln9g9ca4dstDrf+v+qTL3xMbKblBoB3lgiNgzWmWxoy4iLSgQbVHkRxU= Received: from PH0PR18MB4672.namprd18.prod.outlook.com (2603:10b6:510:c9::16) by DM4PR18MB5194.namprd18.prod.outlook.com (2603:10b6:8:53::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5293.13; Fri, 27 May 2022 07:27:47 +0000 Received: from PH0PR18MB4672.namprd18.prod.outlook.com ([fe80::141b:43fb:348e:f3a]) by PH0PR18MB4672.namprd18.prod.outlook.com ([fe80::141b:43fb:348e:f3a%5]) with mapi id 15.20.5293.013; Fri, 27 May 2022 07:27:47 +0000 From: Anoob Joseph To: "Kusztal, ArkadiuszX" , Akhil Goyal , "dev@dpdk.org" , Kiran Kumar Kokkilagadda CC: "Zhang, Roy Fan" , Umesh Kartha , Ramkumar Balu Subject: RE: [EXT] [PATCH 11/40] cryptodev: remove asym crypto next xform Thread-Topic: [EXT] [PATCH 11/40] cryptodev: remove asym crypto next xform Thread-Index: AQHYbBelwNWHI0EqxEqJyWBKRfYRyq0t5jIAgAA7+gCAAQCsAIAACHaAgAAERNCAAx7XAIAAAq4AgAAEQ4CAAAfwIA== Date: Fri, 27 May 2022 07:27:46 +0000 Message-ID: References: <20220520055445.40063-1-arkadiuszx.kusztal@intel.com> <20220520055445.40063-12-arkadiuszx.kusztal@intel.com> In-Reply-To: Accept-Language: en-IN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: c3495b59-947b-4096-1764-08da3fb265de x-ms-traffictypediagnostic: DM4PR18MB5194:EE_ x-microsoft-antispam-prvs: x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: HHoMOYhCvYyfVu+UcKrvv3R8MClBL5sh7naoo8TUHmLczRZTERKM7N31zlFifCDyoNAtzHE72yd/Sl40ld8Ku9x3MWHm5FhFDKYOqn3ICkJWHGaSTl1BOQwrOQ6F4tIllTn81INsRZomQOp4ZnznHHjSHsAt8KVsToLwj9ptZpQJbStDrGp2+PBl1MlDkT8wnNtLuQvi3dy/Ucg0QfyXa9bwnyJvMV5QQfV6oCcU+lcoRT4mIQURO119OE+BxAr49cwC62O39fYjqTfjnkZFvjRnmKHDVh4S5TE79EyE15wdDpkUn/2um2KvHowEMipdxvcshxyFStkIJ/D/nIHsyHUvz5N7r6Y8OYkTv5IKpNF8dImBsf0oe43iLnGEukf6bRu1XshEedv1rVHVJ+vQnZeNG7IiBdFsPBMhFCyeVkm9vNNUwGILGO/Art8XnhmuSzqznBQMLge4dXmBeCswWnqK/E4hRfycP/u6tAoWf9T+NR72vhuNJ0au3H3nQkIx4Ddv/3BGxJ5gaxlylKcpkOxIkUafq76O41AyisCHeWT8Rd97pZUWXK9Ye3ErvJIgdqodI9hH1NZsRoJBZVzeO3miybNBuAWM4rRRG1v6AlYw/+fsmCVWkHqWhnuiWKlej30c6AtQRc/Gh9heTE+Zj8/dwiHlcZi2QYt+LGzQ7YKdqcitSzeh0iH0neraNwlaJ7quYIvZj9Rb1ETvbklbp8wOTZZ/WovMZaR0vRUnObkrqhGPJsp49TkFDeGUwEP+bTd3Qxug39l2/JLV8nPLU8/0DjezDGwccW5ugKGqVaQ= x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PH0PR18MB4672.namprd18.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(4636009)(366004)(64756008)(76116006)(4326008)(66476007)(66946007)(66556008)(66446008)(38070700005)(8676002)(83380400001)(2906002)(9686003)(71200400001)(7696005)(33656002)(5660300002)(8936002)(966005)(26005)(86362001)(6636002)(6506007)(508600001)(38100700002)(316002)(52536014)(19627235002)(107886003)(53546011)(55016003)(54906003)(110136005)(122000001)(186003); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?PU9xkPUR9d5fkEM9PADfhRYEHqmRIPDg7q2dKVLc5VNTHplSKw/Tk7zuQQYy?= =?us-ascii?Q?33/u2bCBIJXSKDqkK3BR1VBWOOvd5ze6Ft3dANFsE08XOuo4YrOBIqlCvPHl?= =?us-ascii?Q?qUhCk0/wvnFPam/r7q7YNCP4GwPtqwC6bz9mPTRu98oT7ia/QqZWADldpSfG?= =?us-ascii?Q?W7+bKTcnJSU5qzDWTzti8nuxhWi3neqCmgEHRbVivMThb7tkrJlBMrt6lt0V?= =?us-ascii?Q?UFTYEUHZDqnRDuL3h3cTCTRwm0RA96lKddJq2DY8YH7nx8YBjSCHUxElYegj?= =?us-ascii?Q?JmfOAwPaPm8sXbQnuIt6gl9CQFPxpg6/ME3Vo92OQxfzuE/Vaqezvd4TQPJ8?= =?us-ascii?Q?HZz4TRKMYA48QbTGZN66j43lOkBo3Zs/DuhEP4YHleSFKKONuaizyIOwVNyY?= =?us-ascii?Q?aoCEMEPblGAP0isBOae+UH/o45P8DEVXMoWLj3ryhuknCHCZUbv1nkIALRoT?= =?us-ascii?Q?nYRfWBaKBRvWPF4vGHnCcYNhTV0p2/8JZLDfMwGfTHJemWiyqefNLJUu5GEy?= =?us-ascii?Q?sO8x6aAaBkppsRA5/IVBQrNaehG5+VSfaWLoyS7EuAftEFAJDPUzkZi5fOT3?= =?us-ascii?Q?vaE3QDKIq3UVZmoITPgcb+tYwWWSd4antNKFFe8kD05sC1T5q95M9hO1Fn0A?= =?us-ascii?Q?emUiUUAWyiu2JSO/TQ6J8eqP9DJhYYldrA4GrGXlNd7zMI1sHkWTUK1489sA?= =?us-ascii?Q?Up8GMnKgqoU7UymfDbqNsLm5Vgvi/xW0DEfSQX3igihzRS5SKgv3k4fpT94m?= =?us-ascii?Q?M5srQWCzVIV6OkIsH1WNZ9nrclErJL8hs+Uj7IUE6wPaZNgh46Wjm40zcWPR?= =?us-ascii?Q?uCTAXPWwId90Wxa0hKWxrgZMH2a8I2BQE7qhwby/CiL/LL/Ry2B51WdsZHKe?= =?us-ascii?Q?y54E6CVpBjbraPrmtT6Z25Eq5jfwbc0SSGvpjojsIpzvbvFaYZn5LKy/Y56/?= =?us-ascii?Q?0v0QrQhGlGQAqPT95AnwXAn3mnmnwZ3HzszzhsYDYCfTkd4g/RdHHRgp9jmC?= =?us-ascii?Q?3CsySv+vNskQp5gBi7Jv29dB6k3M0T2LwpiFvEhLi3Vpw5oTWFDwrMiwNb/Y?= =?us-ascii?Q?35nSxz793Ip+cOsiG3wGQ5KeFHIaXJIJp24drH6aPrYkbgMrBNp51enTEgfh?= =?us-ascii?Q?w/SPV357OiOIjZXLzdOuY1pcbo9xJN+5zbOuDZpqWGc6j1O3td3JNk3nyj+M?= =?us-ascii?Q?9cpxqdl3H+WJeGbbBXqzx/s3CXmQv/v8f1rkhNA7r76k86Okkusp8UBzjg+b?= =?us-ascii?Q?2lM1ggQ8HufU6lRaj96KRR663y5u95MRFWgX3hUScFZdVISR8JKJsYpTthXJ?= =?us-ascii?Q?aJbYXEAft/3CitlTBCq7gEpfCvUGlGCQlN970fO/i4aH0U1g/cBZ+01wLnU3?= =?us-ascii?Q?kvJf9j3X88VRO5mehR8876fOQrqtgQ6pz7laZAKcCBdzLGDBZwUGXTr4WhMz?= =?us-ascii?Q?VAMRC9Rlb+DTY8+aX94Hby0ih2lwfQ+cgWPbAThuHkOT1p4agiXgSGoO470D?= =?us-ascii?Q?W/5SleaGp5vXJ7V0vP9qsCslFxm2v+dgA1qGTpOGzrXn9LsdTpDnsv8BoiCx?= =?us-ascii?Q?qkFnTIRQ9WMryE1tXv58d+DVTTBfD0+WR2cf8ybR9aCujsPY+y2KTCTJMFz5?= =?us-ascii?Q?/UDl80+l7n2FnZzGcmhHWhCbbViWcmNDDzGVgqBPxB13B/xo837EEdZvyGbb?= =?us-ascii?Q?aSkwjhJtJmvxJccr+ELbKHo6Y4b/wSlOuODtBHYdq08pIZjC4sbfm26P4E5l?= =?us-ascii?Q?orZTcNmdPg=3D=3D?= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: marvell.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: PH0PR18MB4672.namprd18.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: c3495b59-947b-4096-1764-08da3fb265de X-MS-Exchange-CrossTenant-originalarrivaltime: 27 May 2022 07:27:47.1503 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 70e1fb47-1155-421d-87fc-2e58f638b6e0 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: UKjnflu7PP8zhMyJ2FlCckZkXwkyDkpzMXfoqJ1Uk/eQM24pFtih2BCTgE9d5Vu6yq52Ai0AavqE5XbHEAxz+w== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR18MB5194 X-Proofpoint-GUID: IW5b6FyDSHskSe1oMU8HKUw99GyHgHg5 X-Proofpoint-ORIG-GUID: IW5b6FyDSHskSe1oMU8HKUw99GyHgHg5 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.874,Hydra:6.0.486,FMLib:17.11.64.514 definitions=2022-05-27_02,2022-05-25_02,2022-02-23_01 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi Arek, Please see inline. Thanks, Anoob > -----Original Message----- > From: Kusztal, ArkadiuszX > Sent: Friday, May 27, 2022 12:26 PM > To: Anoob Joseph ; Akhil Goyal ; > dev@dpdk.org; Kiran Kumar Kokkilagadda > Cc: Zhang, Roy Fan ; Umesh Kartha > ; Ramkumar Balu > Subject: RE: [EXT] [PATCH 11/40] cryptodev: remove asym crypto next xform >=20 >=20 >=20 > > -----Original Message----- > > From: Kusztal, ArkadiuszX > > Sent: Friday, May 27, 2022 8:40 AM > > To: Anoob Joseph ; Akhil Goyal > > ; dev@dpdk.org; Kiran Kumar Kokkilagadda > > > > Cc: Zhang, Roy Fan ; Umesh Kartha > > ; Ramkumar Balu > > Subject: RE: [EXT] [PATCH 11/40] cryptodev: remove asym crypto next > > xform > > > > > > > > > -----Original Message----- > > > From: Kusztal, ArkadiuszX > > > Sent: Friday, May 27, 2022 8:31 AM > > > To: Anoob Joseph ; Akhil Goyal > > > ; dev@dpdk.org; Kiran Kumar Kokkilagadda > > > > > > Cc: Zhang, Roy Fan ; Umesh Kartha > > > ; Ramkumar Balu > > > Subject: RE: [EXT] [PATCH 11/40] cryptodev: remove asym crypto next > > > xform > > > > > > Hi Anoob, > > > > > > Sorry, I don't know how I have missed this email! > > > > > > > -----Original Message----- > > > > From: Anoob Joseph > > > > Sent: Wednesday, May 25, 2022 9:06 AM > > > > To: Kusztal, ArkadiuszX ; Akhil > > > > Goyal ; dev@dpdk.org; Kiran Kumar Kokkilagadda > > > > > > > > Cc: Zhang, Roy Fan ; Umesh Kartha > > > > ; Ramkumar Balu > > > > Subject: RE: [EXT] [PATCH 11/40] cryptodev: remove asym crypto > > > > next xform > > > > > > > > Hi Arek, Akhil, > > > > > > > > Please see inline. > > > > > > > > Thanks, > > > > Anoob > > > > > > > > > -----Original Message----- > > > > > From: Kusztal, ArkadiuszX > > > > > Sent: Wednesday, May 25, 2022 12:06 PM > > > > > To: Akhil Goyal ; dev@dpdk.org; Kiran Kumar > > > > > Kokkilagadda ; Anoob Joseph > > > > > > > > > > Cc: Zhang, Roy Fan > > > > > Subject: RE: [EXT] [PATCH 11/40] cryptodev: remove asym crypto > > > > > next xform > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Akhil Goyal > > > > > > Sent: Wednesday, May 25, 2022 8:06 AM > > > > > > To: Kusztal, ArkadiuszX ; > > > > > > dev@dpdk.org; Kiran Kumar Kokkilagadda > > > > > > ; Anoob Joseph > > > > > > Cc: Zhang, Roy Fan > > > > > > Subject: RE: [EXT] [PATCH 11/40] cryptodev: remove asym crypto > > > > > > next xform > > > > > > > > > > > > > > > - removed asymnetric crypto xform next field. > > > > > > > > > Rationale behind having chaining in symmetric crypto was > > > > > > > > > a fact that encryption and authentication are usually > > > > > > > > > done on the same set of data independent of algorithm. > > > > > > > > > HW usually will be able to handle it in one PCI call. > > > > > > > > > In asymmetric there is no such relation between > > > > > > > > > algorithms, therefore next field would be useless. > > > > > > > > > > > > > > > > > > Signed-off-by: Arek Kusztal > > > > > > > > > > > > > > > > > > > > > > > > > Please check documentation > > > "doc/guides/prog_guide/cryptodev_lib.rst" > > > > > > > > Not all asymmetric crypto xforms are supported for chaining= . > > > > > > > > Currently supported asymmetric crypto chaining is > > > > > > > > Diffie-Hellman private key generation followed by public > generation. > > > > > > > [Arek] And why do chaining when this can be done even with > > > > > > > one bit > > flag. > > > > > > > > > > > > > I believe it is OK to remove next. @Kiran Kumar > > > > > > Kokkilagadda/Anoob please confirm. > > > > > > > > > > > > If we are removing it, then documentation should be in sync. > > > > > [Arek] - although, we may keep it for now, I am not dropping it i= n v2. > > > > > DH priv + pub can be done with priv_key.len =3D 0 -> similar as '= k' > > > > > in ecdsa when k.data =3D NULL. > > > > > But I do not see any situation for now it will be useful, it > > > > > may be dropped later if not application found. > > > > > > > > > > > > > Also, currently API does not support chaining of > > > > > > > > symmetric and asymmetric crypto xforms. > > > > > > > [Arek] - This is one unlikely scenario to combine symmetric > > > > > > > and asymmetric. One I can think of was once proposed DH + > > > > > > > DSA integration for random number. But not much else, > > > > > > > although we can keep it around for a > > > > > > while. > > > > > > > > > > > > Yes it is highly unlikely to use this combination. > > > > > > > > [Anoob] We may need this support when we add EdDSA support. That > > > > would involve a asymmetric operation after hash is generated (symme= tric). > > > > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__en.wikipedia= . > > > > org_wiki_EdDSA- > 23Ed25519&d=3DDwIFAg&c=3DnKjWec2b6R0mOyPaz7xtfQ&r=3DjPfB8 > > > > rwwviRSxyLWs2n6B- > WYLn1v9SyTMrT5EQqh2TU&m=3DbddkY8ZMMGGHjFFvgGsyhfgWB > > > > fuX0hpwqTdpgCAo_ngHINhO6zwLB- > mUxNU8xu6p&s=3D3vFaBffulofGlfAPsjnaaUZa > > > > V01o6k8XWzwNFWHQzvY&e=3D > > > > > > > > And, asymmetric chaining may become useful when we have PMDs > > > > capable of doing more operations together (like the case with > > > > EdDSA). So my preference would be to retain the 'next' field in asy= m crypto > xform. > > > [Arek] - that is very good point, however to implement EdDSA as > > > chaining would mean that: > > > - we need to implement EdDSA internals in DPDK > > > - and EdDSA (in hash option, where actually picking hash would have > > > sense) is not one hash but multiple hash operation, so we would have > > > to had multiple chaining with operations in between > > > - and we would have to compute R and S separately. > > > - If PMD does not support one-pass EdDSA - well this is something > > > that should definitely discuss, but having any crypto internals in > > > DPDK is not probably an option? > > [Arek] - but, I have kept 'next' in later changes. > [Arek] - additionally if EdDSAhash one-pass used it is enough to have fie= ld with > hash, an that's all - only information needed. > Normally EdDSA hash is fixed to SHA256 or BLAKE but for EdDSAhash option > there is one additional hash - so enum in Ed struct should be enough. [Anoob] I'm also not clear about what would be the right abstraction. As yo= u described for EdDSA, it can be just a flag. But we may need to revisit th= is when we add such kind of algos. So my suggestion was to not remove 'next= ' field just yet. We can revisit this sometime later. Thanks for agreeing to the suggestion and keeping the field. =20 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --- > > > > > > > > > lib/cryptodev/rte_crypto_asym.h | 2 -- > > > > > > > > > 1 file changed, 2 deletions(-) > > > > > > > > > > > > > > > > > > diff --git a/lib/cryptodev/rte_crypto_asym.h > > > > > > > > > b/lib/cryptodev/rte_crypto_asym.h index > > > > > > > > > 1652a434a5..b355cbe5fa > > > > > > > > > 100644 > > > > > > > > > --- a/lib/cryptodev/rte_crypto_asym.h > > > > > > > > > +++ b/lib/cryptodev/rte_crypto_asym.h > > > > > > > > > @@ -492,8 +492,6 @@ struct rte_crypto_ecpm_op_param { > > > > > > > > > * Structure describing asym xforms. > > > > > > > > > */ > > > > > > > > > struct rte_crypto_asym_xform { > > > > > > > > > - struct rte_crypto_asym_xform *next; > > > > > > > > > - /**< Pointer to next xform to set up xform chain.*/ > > > > > > > > > enum rte_crypto_asym_xform_type xform_type; > > > > > > > > > /**< Asymmetric crypto transform */ > > > > > > > > > > > > > > > > > > -- > > > > > > > > > 2.13.6