> -----Original Message-----
> From: Power, Ciara <ciara.po...@intel.com>
> Sent: Monday, January 24, 2022 3:04 PM
> To: dev@dpdk.org
> Cc: Zhang, Roy Fan <roy.fan.zh...@intel.com>; gak...@marvell.com;
> ano...@marvell.com; m...@ashroe.eu; Power, Ciara
> <ciara.po...@intel.com>; Doherty, Declan <declan.dohe...@intel.com>;
> Ankur Dwivedi <adwiv...@marvell.com>; Tejasree Kondoj
> <ktejas...@marvell.com>; Griffin, John <john.grif...@intel.com>; Trahe,
> Fiona <fiona.tr...@intel.com>; Jain, Deepak K <deepak.k.j...@intel.com>
> Subject: [PATCH v2 1/4] crypto: use single buffer for asymmetric session
>
> Rather than using a session buffer that contains pointers to private
> session data elsewhere, have a single session buffer.
> This session is created for a driver ID, and the mempool element
> contains space for the max session private data needed for any driver.
>
> Signed-off-by: Ciara Power <ciara.po...@intel.com>
>
> ---
Although Anoob had slightly different idea on missed iova address to the
session private data,
the general approach looks ok to me.
Acked-by: Fan Zhang <roy.fan.zh...@intel.com>
