> -----Original Message-----
> From: Akhil Goyal <[email protected]>
> Sent: Tuesday, September 27, 2022 3:14 AM
> To: [email protected]
> Cc: [email protected]; [email protected]; [email protected];
> [email protected]; [email protected]; [email protected];
> [email protected]; [email protected]; 
> [email protected];
> [email protected]; [email protected]; [email protected];
> [email protected]; [email protected]; Ruifeng Wang 
> <[email protected]>; Ajit
> Khaparde ([email protected]) <[email protected]>; 
> [email protected];
> [email protected]; [email protected]; [email protected]; 
> [email protected];
> [email protected]; [email protected]; [email protected];
> [email protected]; [email protected]; [email protected]; 
> Akhil Goyal
> <[email protected]>
> Subject: [PATCH v4 0/6] crypto/security session framework rework
> 
> This patchset reworks the symmetric crypto and security session data 
> structure to use a
> single virtual/physical contiguous buffer for symmetric crypto/security 
> session and driver
> private data.
> In addition the session data structure is now private.
> The session is represented as an opaque pointer in the application.
> 
> With the change the session is no longer supported to be accessed by multiple 
> device
> drivers. For the same reason rte_cryptodev_sym_session_init/clear APIs are 
> deprecated as
> rte_cryptodev_sym_session_create/free will initialize and clear the driver 
> specific data
> field.
> 
> The change was also submitted last year during DPDK 21.11 timeframe also[1], 
> but was not
> applied due to lack of feedback from community. Please help in getting this 
> cleanup merged
> in this cycle.
> 
> Now the similar work was already done for asymmetric crypto.
> This patchset is rebased over current tree and fixes all the issues reported 
> so far.
> 
> Changes in v4:
> - squashed armv8_crypto fixes.
> http://patches.dpdk.org/project/dpdk/cover/[email protected]/
> 

Verified for armv8 crypto PMD. Test cases are passing.
For the series,
Tested-by: Ruifeng Wang <[email protected]>

Thanks,
Ruifeng

Reply via email to