Re: [dpdk-dev] [PATCH v2] ethdev: remove driver name from device private data

2017-06-09 Thread Ferruh Yigit
On 6/9/2017 3:22 PM, Ferruh Yigit wrote: > On 6/7/2017 5:11 PM, Jan Blunck wrote: >> On Tue, Jun 6, 2017 at 5:10 PM, Ferruh Yigit wrote: >>> rte_driver->name has the driver name and all physical and virtual >>> devices has access to it. >>> >>> Previously it was not possible for virtual ethernet d

Re: [dpdk-dev] [PATCH v2] ethdev: remove driver name from device private data

2017-06-09 Thread Ferruh Yigit
On 6/7/2017 5:11 PM, Jan Blunck wrote: > On Tue, Jun 6, 2017 at 5:10 PM, Ferruh Yigit wrote: >> rte_driver->name has the driver name and all physical and virtual >> devices has access to it. >> >> Previously it was not possible for virtual ethernet devices to access >> rte_driver->name field (beca

Re: [dpdk-dev] [PATCH v2] ethdev: remove driver name from device private data

2017-06-09 Thread Ferruh Yigit
On 6/8/2017 9:58 PM, Thomas Monjalon wrote: > 06/06/2017 17:10, Ferruh Yigit: >> rte_driver->name has the driver name and all physical and virtual >> devices has access to it. >> >> Previously it was not possible for virtual ethernet devices to access >> rte_driver->name field (because eth_dev used

Re: [dpdk-dev] [PATCH v2] ethdev: remove driver name from device private data

2017-06-08 Thread Thomas Monjalon
06/06/2017 17:10, Ferruh Yigit: > rte_driver->name has the driver name and all physical and virtual > devices has access to it. > > Previously it was not possible for virtual ethernet devices to access > rte_driver->name field (because eth_dev used to keep only pci_dev), > and it was required to s

Re: [dpdk-dev] [PATCH v2] ethdev: remove driver name from device private data

2017-06-07 Thread Jan Blunck
On Tue, Jun 6, 2017 at 5:10 PM, Ferruh Yigit wrote: > rte_driver->name has the driver name and all physical and virtual > devices has access to it. > > Previously it was not possible for virtual ethernet devices to access > rte_driver->name field (because eth_dev used to keep only pci_dev), > and

Re: [dpdk-dev] [PATCH v2] ethdev: remove driver name from device private data

2017-06-06 Thread Shreyansh Jain
On Tuesday 06 June 2017 08:40 PM, Ferruh Yigit wrote: rte_driver->name has the driver name and all physical and virtual devices has access to it. Previously it was not possible for virtual ethernet devices to access rte_driver->name field (because eth_dev used to keep only pci_dev), and it was r

Re: [dpdk-dev] [PATCH v2] ethdev: remove driver name from device private data

2017-06-06 Thread Gaëtan Rivet
Hi Ferruh, On Tue, Jun 06, 2017 at 04:10:08PM +0100, Ferruh Yigit wrote: > rte_driver->name has the driver name and all physical and virtual > devices has access to it. > > Previously it was not possible for virtual ethernet devices to access > rte_driver->name field (because eth_dev used to keep

[dpdk-dev] [PATCH v2] ethdev: remove driver name from device private data

2017-06-06 Thread Ferruh Yigit
rte_driver->name has the driver name and all physical and virtual devices has access to it. Previously it was not possible for virtual ethernet devices to access rte_driver->name field (because eth_dev used to keep only pci_dev), and it was required to save driver name in the device private struct