Re: [dpdk-dev] [PATCH v3 6/8] cryptodev: rework session framework

2021-10-21 Thread Ananyev, Konstantin
> > The problem is that with new approach you proposed there is no simple way > > for PMD to > > fulfil that requirement. > > In current version of DPDK: > > - PMD reports size of private data, note that it reports extra space needed > >to align its data properly inside provided buffer. > >

Re: [dpdk-dev] [PATCH v3 6/8] cryptodev: rework session framework

2021-10-21 Thread Akhil Goyal
> The problem is that with new approach you proposed there is no simple way > for PMD to > fulfil that requirement. > In current version of DPDK: > - PMD reports size of private data, note that it reports extra space needed >to align its data properly inside provided buffer. > - Then it ss up t

Re: [dpdk-dev] [PATCH v3 6/8] cryptodev: rework session framework

2021-10-21 Thread Ananyev, Konstantin
> > > As per current design, rte_cryptodev_sym_session_create() and > > > rte_cryptodev_sym_session_init() use separate mempool objects > > > for a single session. > > > And structure rte_cryptodev_sym_session is not directly used > > > by the application, it may cause ABI breakage if the structu

Re: [dpdk-dev] [PATCH v3 6/8] cryptodev: rework session framework

2021-10-20 Thread Akhil Goyal
> > As per current design, rte_cryptodev_sym_session_create() and > > rte_cryptodev_sym_session_init() use separate mempool objects > > for a single session. > > And structure rte_cryptodev_sym_session is not directly used > > by the application, it may cause ABI breakage if the structure > > is

Re: [dpdk-dev] [PATCH v3 6/8] cryptodev: rework session framework

2021-10-20 Thread Ananyev, Konstantin
Hi Akhil, > As per current design, rte_cryptodev_sym_session_create() and > rte_cryptodev_sym_session_init() use separate mempool objects > for a single session. > And structure rte_cryptodev_sym_session is not directly used > by the application, it may cause ABI breakage if the structure > is