> -----Original Message-----
> From: Akhil Goyal <[email protected]>
> Sent: Thursday, April 21, 2022 3:37 PM
> To: [email protected]
> Cc: [email protected]; [email protected]; Gujjar, Abhinandan S
> <[email protected]>; Jayatheerthan, Jay
> <[email protected]>; Vangati, Narender
> <[email protected]>; [email protected]; Akhil Goyal
> <[email protected]>
> Subject: [PATCH v3 1/7] cryptodev: add APIs to get/set event metadata
>
> From: Volodymyr Fialko <[email protected]>
>
> Currently, crypto session userdata is used to set event crypto
> metadata from the application and the driver is dereferencing it
> in driver which is not correct. User data is meant to be opaque
> to the driver.
> To support this, new API is added to get and set event crypto
> metadata. The new API, rte_cryptodev_set_session_event_mdata,
> allows setting event metadata in session private data which is
> filled inside PMD using a new cryptodev op. This operation
> can be performed on any of the PMD supported sessions
> (sym/asym/security).
> For SW abstraction of event crypto adapter to be used by
> eventdev library, a new field is added in asymmetric crypto
> session for now and for symmetric case, current implementation
> of using userdata is used. Symmetric cases cannot be fixed now,
> as it will be ABI breakage which will be resolved in DPDK 22.11.
>
> Signed-off-by: Volodymyr Fialko <[email protected]>
> Signed-off-by: Akhil Goyal <[email protected]>
> ---
Acked-by: Fan Zhang <[email protected]>
