subject:"\[dpdk\-dev\] \[PATCH v2\] cryptodev\: fix check related to device id"

Re: [dpdk-dev] [PATCH v2] cryptodev: fix check related to device id

2019-10-16 Thread Meunier, Julien (Nokia - FR/Paris-Saclay)

Hi, Inline reply On 16/10/2019 09:02, Akhil Goyal wrote: > Hi Julien, > > A couple of nits. Please see inline. > > Apart from that > Acked-by: Akhil Goyal > >> >> Each cryptodev are indexed with dev_id in the global rte_crypto_devices >> variable. nb_devs is incremented / decremented each tim

Re: [dpdk-dev] [PATCH v2] cryptodev: fix check related to device id

2019-10-16 Thread Akhil Goyal

Hi Julien, A couple of nits. Please see inline. Apart from that Acked-by: Akhil Goyal > > Each cryptodev are indexed with 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 was to prevent th

[dpdk-dev] [PATCH v2] cryptodev: fix check related to device id

2019-10-15 Thread Julien Meunier

Each cryptodev are indexed with 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 was to prevent the user to get an invalid dev_id. Let's imagine DPDK has configured N cryptodevs. If the cryptodev=