[ovs-discuss] ovs-vswitchd support of more than 32 physical devices?

[Daniele Di Proietto]

This appears to be a limitation in the DPDK library:

I see possible two solutions:

1) Recompile DPDK with CONFIG_RTE_MAX_ETHPORTS > 32
2) Use "--pci-blacklist" DPDK option to limit the number of ports detected
by DPDK

On 03/03/2016 10:10, "discuss on behalf of John Wei"
<discuss-bounces at openvswitch.org on behalf of johntwei at gmail.com> wrote:

>I am setting up OVS in container on the host with 126 SRIOV VFs, all
>these VFs are bounded to DPDK.
>Each OVS in a container will be using just two VFs. But, all 126 VFs are
>visible to each container. I have not find ways to make VFs be
>selectively visible in the container.
>
>It seems that ovs-vswitchd is not able to deal with more than 32 DPDK
>ports.
>
>When starting ovs-vswitchd, it was able to deal with port 0-31. I died
>when dealing with 32nd port:
>......
>
>PMD: eth_ixgbevf_dev_init(): port 31 vendorID=0x8086 deviceID=0x10ed
>mac.type=ixgbe_mac_82599_vf
>EAL: PCI device 0000:42:14.0 on NUMA socket 1
>EAL:   probe driver: 8086:10ed rte_ixgbevf_pmd
>EAL:   PCI memory mapped at 0x7f10e8f00000
>EAL:   PCI memory mapped at 0x7f10e8f04000
>EAL: Error - exiting with code: 1
>  Cause: Requested device 0000:42:14.0 cannot be used
>
>Is there a parameter or code some where I can increase the number of
>ports that vswitchd can deal with?
>
>Or, can I ask ovs-vswitchd to scan just a few ports?
>
>
>The same issue exists when running OVS on host with more than 32 DPDK
>ports.
>
>
>
>John
>
>