[PATCH v2 1/6] cryptodev: rework session framework

[Ji, Kai]

Acked-by: Kai Ji <kai.ji at intel.com>

> -----Original Message-----
> From: Akhil Goyal <gakhil at marvell.com>
> Sent: Wednesday, September 21, 2022 4:03 PM
> To: dev at dpdk.org
> Cc: thomas at monjalon.net; david.marchand at redhat.com;
> hemant.agrawal at nxp.com; vattunuru at marvell.com;
> ferruh.yigit at xilinx.com; andrew.rybchenko at oktetlabs.ru;
> konstantin.v.ananyev at yandex.ru; jiawenwu at trustnetic.com;
> yisen.zhuang at huawei.com; irusskikh at marvell.com; jerinj at marvell.com;
> adwivedi at marvell.com; maxime.coquelin at redhat.com; chandu at amd.com;
> ruifeng.wang at arm.com; ajit.khaparde at broadcom.com;
> anoobj at marvell.com; De Lara Guarch, Pablo
> <pablo.de.lara.guarch at intel.com>; matan at nvidia.com; g.singh at nxp.com;
> Yang, Qiming <qiming.yang at intel.com>; Wu, Wenjun1
> <wenjun1.wu at intel.com>; jianwang at trustnetic.com; Wu, Jingjing
> <jingjing.wu at intel.com>; Xing, Beilei <beilei.xing at intel.com>;
> ndabilpuram at marvell.com; Akhil Goyal <gakhil at marvell.com>; Zhang, Roy
> Fan <roy.fan.zhang at intel.com>
> Subject: [PATCH v2 1/6] cryptodev: rework session framework
> 
> As per current design, rte_cryptodev_sym_session_create() and
> rte_cryptodev_sym_session_init() use separate mempool objects
> for a single session.
> And structure rte_cryptodev_sym_session is not directly used
> by the application, it may cause ABI breakage if the structure
> is modified in future.
> 
> To address these two issues, the rte_cryptodev_sym_session_create
> will take one mempool object that the session and session private
> data are virtually/physically contiguous, and initializes both
> fields. The API rte_cryptodev_sym_session_init is removed.
> 
> rte_cryptodev_sym_session_create will now return an opaque session
> pointer which will be used by the app and other APIs.
> 
> In data path, opaque session pointer is attached to rte_crypto_op
> and the PMD can call an internal library API to get the session
> private data pointer based on the driver id.
> 
> Note: currently single session may be used by different device
> drivers, given it is initialized by them. After the change the
> session created by one device driver cannot be used or
> reinitialized by another driver.
> 
> Signed-off-by: Akhil Goyal <gakhil at marvell.com>
> Signed-off-by: Fan Zhang <roy.fan.zhang at intel.com>
> ---