[dpdk-dev] [PATCH v3 0/4] add AESNI-MB rawdev for multi-function processing

[Zhang, Roy Fan]

Hi Akhil,

> -----Original Message-----
> From: dev <dev-bounces at dpdk.org> On Behalf Of Akhil Goyal
> Sent: Wednesday, April 22, 2020 2:44 PM
> To: Coyle, David <david.coyle at intel.com>; Doherty, Declan
> <declan.doherty at intel.com>; Thomas Monjalon <thomas at monjalon.net>;
> Yigit, Ferruh <ferruh.yigit at intel.com>; Trahe, Fiona <fiona.trahe at intel.com>
> Cc: techboard at dpdk.org; dev at dpdk.org; De Lara Guarch, Pablo
> <pablo.de.lara.guarch at intel.com>; Ryan, Brendan
> <brendan.ryan at intel.com>; Hemant Agrawal <hemant.agrawal at nxp.com>;
> Anoob Joseph <anoobj at marvell.com>; Ruifeng Wang
> <ruifeng.wang at arm.com>; Liron Himi <lironh at marvell.com>; Nagadheeraj
> Rottela <rnagadheeraj at marvell.com>; Srikanth Jampala
> <jsrikanth at marvell.com>; Gagandeep Singh <G.Singh at nxp.com>; Jay Zhou
> <jianjay.zhou at huawei.com>; Ravi Kumar <ravi1.kumar at amd.com>;
> Richardson, Bruce <bruce.richardson at intel.com>; olivier.matz at 6wind.com;
> honnappa.nagarahalli at arm.com; Stephen Hemminger
> <stephen at networkplumber.org>; alexr at mellanox.com
> Subject: Re: [dpdk-dev] [PATCH v3 0/4] add AESNI-MB rawdev for multi-
> function processing
...
> Yes, it is preferred, but it should be a union to
> rte_crypto_sym_op/rte_crypto_asym_op.
> Crypto_op->type as RTE_CRYPTO_OP_TYPE_SECURITY and sess_type as
> RTE_CRYPTO_OP_SECURITY_SESSION
> The size of rte_crypto_op will remain as is and there will be no ABI breakage I
> guess.
> 
[Fan: with this way the PMD will have to do rte_crypto_op.type check, and then look into rte_security_op field, only when it find the security_op type is crypto_crc, it will process the security_op data. Would that being too many reads and checking for a single op? Can we create a new API for rte_security to process rte_security_ops for Crypto_CRC or future needs?]
...
 
Regards,
Fan