[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-29 Thread Andriy Berestovskyy
Hey folks, > On 28 Jul 2016, at 17:47, De Lara Guarch, Pablo intel.com> wrote: > Fair enough. So you mean to use rte_eth_dev_attach in ethdev library and > a similar function in cryptodev library? There is a rte_eth_dev_get_port_by_name() which gets the port id right after the

[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-28 Thread David Marchand
On Thu, Jul 28, 2016 at 5:47 PM, De Lara Guarch, Pablo wrote: >> This is a layer violation. >> EAL does not know a thing about "ports". >> >> This information should come from the crypto framework and so an api >> in crypto framework is the right place, not EAL. >> >> This is a NACK for me. > >

[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-28 Thread De Lara Guarch, Pablo
> -Original Message- > From: David Marchand [mailto:david.marchand at 6wind.com] > Sent: Thursday, July 28, 2016 5:18 AM > To: De Lara Guarch, Pablo > Cc: dev at dpdk.org; Mcnamara, John > Subject: Re: [dpdk-dev] [PATCH] doc: announce API change for virtual devic

[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-28 Thread David Marchand
Hello Pablo, On Mon, Jul 4, 2016 at 4:50 PM, Pablo de Lara wrote: > In order to create a virtual device, user needs to call > rte_eal_vdev_init generally, but this function returns 0 > on success or negative number if error. Instead, something > more useful would be to return the port or device

[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-06 Thread De Lara Guarch, Pablo
> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of De Lara Guarch, > Pablo > Sent: Tuesday, July 05, 2016 3:55 PM > To: Thomas Monjalon; Yigit, Ferruh > Cc: dev at dpdk.org; Mcnamara, John > Subject: Re: [dpdk-dev] [PATCH] doc: announce A

[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-05 Thread Thomas Monjalon
2016-07-05 14:04, Ferruh Yigit: > On 7/4/2016 3:50 PM, Pablo de Lara wrote: > > +* The rte_eal_vdev_init function will be changed in 16.11 to return > > + the port/device id of the device created, instead of 0, when it has been > > + initialized successfully, so user can use the returned value

[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-05 Thread De Lara Guarch, Pablo
> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Tuesday, July 05, 2016 2:39 PM > To: Yigit, Ferruh > Cc: dev at dpdk.org; De Lara Guarch, Pablo; Mcnamara, John > Subject: Re: [dpdk-dev] [PATCH] doc: announce API change

[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-05 Thread Ferruh Yigit
On 7/4/2016 3:50 PM, Pablo de Lara wrote: > In order to create a virtual device, user needs to call > rte_eal_vdev_init generally, but this function returns 0 > on success or negative number if error. Instead, something > more useful would be to return the port or device id of the > device

[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-05 Thread Declan Doherty
On 04/07/16 15:50, Pablo de Lara wrote: > In order to create a virtual device, user needs to call > rte_eal_vdev_init generally, but this function returns 0 > on success or negative number if error. Instead, something > more useful would be to return the port or device id of the > device created,

[dpdk-dev] [PATCH] doc: announce API change for virtual device initialization

2016-07-04 Thread Pablo de Lara
In order to create a virtual device, user needs to call rte_eal_vdev_init generally, but this function returns 0 on success or negative number if error. Instead, something more useful would be to return the port or device id of the device created, so the user can call rte_eal_vdev_init function