[dpdk-dev] [PATCH] ethdev: support PCI domains

2016-10-04 Thread Thomas Monjalon
2016-07-22 18:56, Sinan Kaya: > On 7/22/2016 5:12 PM, Stephen Hemminger wrote: > > On Fri, 22 Jul 2016 11:34:10 -0400 > > Sinan Kaya wrote: > > > >> The current code is enumerating devices based on bus, device and function > >> pairs. This does not work well for architectures with multiple PCI >

[dpdk-dev] [PATCH] ethdev: support PCI domains

2016-10-04 Thread Sinan Kaya
On 10/4/2016 4:15 AM, Thomas Monjalon wrote: > 2016-07-22 18:56, Sinan Kaya: >> On 7/22/2016 5:12 PM, Stephen Hemminger wrote: >>> On Fri, 22 Jul 2016 11:34:10 -0400 >>> Sinan Kaya wrote: >>> The current code is enumerating devices based on bus, device and function pairs. This does not w

[dpdk-dev] [PATCH] ethdev: support PCI domains

2016-07-22 Thread Sinan Kaya
On 7/22/2016 5:12 PM, Stephen Hemminger wrote: > On Fri, 22 Jul 2016 11:34:10 -0400 > Sinan Kaya wrote: > >> The current code is enumerating devices based on bus, device and function >> pairs. This does not work well for architectures with multiple PCI >> segments/domains. Multiple PCI devices wi

[dpdk-dev] [PATCH] ethdev: support PCI domains

2016-07-22 Thread Stephen Hemminger
On Fri, 22 Jul 2016 11:34:10 -0400 Sinan Kaya wrote: > The current code is enumerating devices based on bus, device and function > pairs. This does not work well for architectures with multiple PCI > segments/domains. Multiple PCI devices will have the same BDF value but > different segment numbe

[dpdk-dev] [PATCH] ethdev: support PCI domains

2016-07-22 Thread Sinan Kaya
The current code is enumerating devices based on bus, device and function pairs. This does not work well for architectures with multiple PCI segments/domains. Multiple PCI devices will have the same BDF value but different segment numbers (01:01:01.0 and 02:01:01.0) for instance. Adding segment nu