Re: [dpdk-dev] [PATCH] ethdev: fix port ID retrieval on vdev attach

2018-07-11 Thread Andrew Rybchenko
On 11.07.2018 13:52, Thomas Monjalon wrote: 11/07/2018 12:15, Andrew Rybchenko: On 11.07.2018 13:02, Thomas Monjalon wrote: 11/07/2018 11:49, Andrew Rybchenko: From: Ivan Malov Attaching a vdev port may result in multiple ports actually added because a vdev port may have slave devices to be

Re: [dpdk-dev] [PATCH] ethdev: fix port ID retrieval on vdev attach

2018-07-11 Thread Thomas Monjalon
11/07/2018 12:15, Andrew Rybchenko: > On 11.07.2018 13:02, Thomas Monjalon wrote: > > 11/07/2018 11:49, Andrew Rybchenko: > >> From: Ivan Malov > >> > >> Attaching a vdev port may result in multiple > >> ports actually added because a vdev port may > >> have slave devices to be attached implicitly

Re: [dpdk-dev] [PATCH] ethdev: fix port ID retrieval on vdev attach

2018-07-11 Thread Andrew Rybchenko
On 11.07.2018 13:02, Thomas Monjalon wrote: 11/07/2018 11:49, Andrew Rybchenko: From: Ivan Malov Attaching a vdev port may result in multiple ports actually added because a vdev port may have slave devices to be attached implicitly. Ethdev attach API has to fill in the port ID to be read back

Re: [dpdk-dev] [PATCH] ethdev: fix port ID retrieval on vdev attach

2018-07-11 Thread Thomas Monjalon
11/07/2018 11:49, Andrew Rybchenko: > From: Ivan Malov > > Attaching a vdev port may result in multiple > ports actually added because a vdev port may > have slave devices to be attached implicitly. > > Ethdev attach API has to fill in the port ID > to be read back by the user and what it does >