Re: [dpdk-dev] [PATCH] doc: announce changes in security session struct

On Tue, Aug 3, 2021 at 5:36 AM Ananyev, Konstantin wrote: > > > > The structure rte_security_session is not directly used > > by the application. The application just need an opaque > > pointer to attached to the mbuf or rte_crypto_op while > > enqueue. Hence, it can be hidden inside the library >

Re: [dpdk-dev] [PATCH] doc: announce changes in security session struct

> The structure rte_security_session is not directly used > by the application. The application just need an opaque > pointer to attached to the mbuf or rte_crypto_op while > enqueue. Hence, it can be hidden inside the library > and would prevent unnecessary indirection to the priv > session data

[dpdk-dev] [PATCH] doc: announce changes in security session struct

The structure rte_security_session is not directly used by the application. The application just need an opaque pointer to attached to the mbuf or rte_crypto_op while enqueue. Hence, it can be hidden inside the library and would prevent unnecessary indirection to the priv session data in fastpath.