Re: [dpdk-dev] [PATCH] cryptodev: fix invalid dev_id after a pmd close

Hi On 15/10/2019 15:44, Akhil Goyal wrote: > >> >> Hi Julien >> >>> >>> Each cryptodev are indexed with its dev_id in the global >>> rte_crypto_devices variable. nb_devs is incremented / decremented each >>> time a cryptodev is created / deleted. The goal of nb_devs is to prevent >>> the user to

Re: [dpdk-dev] [PATCH] cryptodev: fix invalid dev_id after a pmd close

> > Hi Julien > > > > > Each cryptodev are indexed with its dev_id in the global > > rte_crypto_devices variable. nb_devs is incremented / decremented each > > time a cryptodev is created / deleted. The goal of nb_devs is to prevent > > the user to get an invalid dev_id. > > > > Let's imagine D

Re: [dpdk-dev] [PATCH] cryptodev: fix invalid dev_id after a pmd close

Hi Julien > > Each cryptodev are indexed with its dev_id in the global > rte_crypto_devices variable. nb_devs is incremented / decremented each > time a cryptodev is created / deleted. The goal of nb_devs is to prevent > the user to get an invalid dev_id. > > Let's imagine DPDK has configured N

[dpdk-dev] [PATCH] cryptodev: fix invalid dev_id after a pmd close

Each cryptodev are indexed with its dev_id in the global rte_crypto_devices variable. nb_devs is incremented / decremented each time a cryptodev is created / deleted. The goal of nb_devs is to prevent the user to get an invalid dev_id. Let's imagine DPDK has configured N cryptodevs. If the cryptod