> Subject: [PATCH v5 0/7] Add new cryptodev op for event metadata > > For using event crypto metadata, event metadata need to be set > in session. For this session user data was used for symmetric > crypto sessions and no support was present for asymmetric and > security sessions. > The use of userdata to store event metadata (which is dereferenced > in PMD) is not correct as it is meant for the application to use it. > Hence, a new API is created to set and get event crypto metadata which > is scalable to all sessions supported by the crypto PMD. > The application can use the set API to set event metadata and the > PMD may store that inside the session private data and PMD need not > use the get API as it would be internal to the PMD. > For the software event crypto adapter implementation, the eventdev > library can use the get API to get the event metadata stored inside > the session structure. > For Asymmetric sessions, a new field is added inside the session > struct which is internal to library. > For symmetric and security sessions, new field cannot be added as > it would be ABI break. Hence, session userdata is being used to > store that as it was used earlier. In next ABI break release this > would be fixed similar to asymmetric crypto case. > > The patchset also add support for asymmetric crypto adapter > in the test applications and the crypto/cnxk implementation of > the new cryptodev op and corresponding changes in the eventdev lib. > > changes in v5: > removed extra check for freeing mdata
Series Applied to dpdk-next-crypto
