Re: [dpdk-dev] [PATCH v4 4/8] crypto/scheduler: use proper API for device start/stop

2021-10-20 Thread Ananyev, Konstantin
> > The worker PMDs were using direct device start/stop > > functions rather than rte_cryptodev_start(), > > so rte_crypto_fp_ops never get set. This patch calls > > the rte_cryptodev_start and stop APIs which start and > > stop devices properly and fp_ops get set. > > > > Reported-by: Ciara Powe

Re: [dpdk-dev] [PATCH v4 4/8] crypto/scheduler: use proper API for device start/stop

2021-10-20 Thread Zhang, Roy Fan
> -Original Message- > From: Akhil Goyal > Sent: Wednesday, October 20, 2021 12:28 PM > To: dev@dpdk.org > Cc: tho...@monjalon.net; david.march...@redhat.com; > hemant.agra...@nxp.com; ano...@marvell.com; De Lara Guarch, Pablo > ; Trahe, Fiona ; > Doherty, Declan ; ma...@nvidia.com; > g.si

[dpdk-dev] [PATCH v4 4/8] crypto/scheduler: use proper API for device start/stop

2021-10-20 Thread Akhil Goyal
The worker PMDs were using direct device start/stop functions rather than rte_cryptodev_start(), so rte_crypto_fp_ops never get set. This patch calls the rte_cryptodev_start and stop APIs which start and stop devices properly and fp_ops get set. Reported-by: Ciara Power Signed-off-by: Akhil Goyal