Re: [dpdk-dev] [PATCH 2/2] drivers/net: use device name from device structure

2017-06-12 Thread Ferruh Yigit
On 6/10/2017 8:35 AM, Jan Blunck wrote: > On Fri, Jun 9, 2017 at 3:52 PM, Thomas Monjalon wrote: >> 26/05/2017 18:11, Ferruh Yigit: >>> Device name resides in two different locations, in rte_device->name and >>> in ethernet device private data. >> >> Yes would be nice to remove the name from rte_e

Re: [dpdk-dev] [PATCH 2/2] drivers/net: use device name from device structure

2017-06-10 Thread Jan Blunck
On Fri, Jun 9, 2017 at 3:52 PM, Thomas Monjalon wrote: > 26/05/2017 18:11, Ferruh Yigit: >> Device name resides in two different locations, in rte_device->name and >> in ethernet device private data. > > Yes would be nice to remove the name from rte_eth_dev_data. > I wonder if this is really the

Re: [dpdk-dev] [PATCH 2/2] drivers/net: use device name from device structure

2017-06-09 Thread Ferruh Yigit
On 6/9/2017 2:52 PM, Thomas Monjalon wrote: > 26/05/2017 18:11, Ferruh Yigit: >> Device name resides in two different locations, in rte_device->name and >> in ethernet device private data. > > Yes would be nice to remove the name from rte_eth_dev_data. > >> For now, the copy in the ethernet devic

Re: [dpdk-dev] [PATCH 2/2] drivers/net: use device name from device structure

2017-06-09 Thread Thomas Monjalon
26/05/2017 18:11, Ferruh Yigit: > Device name resides in two different locations, in rte_device->name and > in ethernet device private data. Yes would be nice to remove the name from rte_eth_dev_data. > For now, the copy in the ethernet device private data is required for > multi process support,

[dpdk-dev] [PATCH 2/2] drivers/net: use device name from device structure

2017-05-26 Thread Ferruh Yigit
Device name resides in two different locations, in rte_device->name and in ethernet device private data. For now, the copy in the ethernet device private data is required for multi process support, the name is the how secondary process finds about primary process device. But for drivers there is