dpdk eal initialisation takes upwards of 2 minutes during restart

[James Page]

During restarts of ovs, the dpdk EAL init takes a long time:

2018-08-29T16:43:28.945Z|00016|dpdk|INFO|EAL: Probing VFIO support...
2018-08-29T16:45:45.363Z|00017|dpdk|INFO|EAL: PCI device 0000:01:00.0 on NUMA socket 0
2018-08-29T16:45:45.363Z|00018|dpdk|INFO|EAL: probe driver: 8086:10fb net_ixgbe
2018-08-29T16:45:45.363Z|00019|dpdk|INFO|EAL: PCI device 0000:01:00.1 on NUMA socket 0
2018-08-29T16:45:45.363Z|00020|dpdk|INFO|EAL: probe driver: 8086:10fb net_ixgbe
2018-08-29T16:45:45.363Z|00021|dpdk|INFO|EAL: PCI device 0000:03:00.0 on NUMA socket 0
2018-08-29T16:45:45.363Z|00022|dpdk|INFO|EAL: probe driver: 8086:154d net_ixgbe
2018-08-29T16:45:45.363Z|00023|dpdk|INFO|EAL: PCI device 0000:03:00.1 on NUMA socket 0
2018-08-29T16:45:45.363Z|00024|dpdk|INFO|EAL: probe driver: 8086:154d net_ixgbe
2018-08-29T16:45:45.363Z|00025|dpdk|INFO|EAL: PCI device 0000:05:00.0 on NUMA socket 0
2018-08-29T16:45:45.363Z|00026|dpdk|INFO|EAL: probe driver: 8086:1521 net_e1000_igb
2018-08-29T16:45:45.363Z|00027|dpdk|INFO|EAL: PCI device 0000:05:00.1 on NUMA socket 0
2018-08-29T16:45:45.363Z|00028|dpdk|INFO|EAL: probe driver: 8086:1521 net_e1000_igb
2018-08-29T16:45:45.363Z|00029|dpdk|INFO|DPDK pdump packet capture enabled
2018-08-29T16:45:45.370Z|00030|dpdk|INFO|DPDK Enabled - initialized

This can be reduced by passing the pci-whitelist configuration to OVS, so that only whitelisted devices are scanned for VFIO support.

[James Page (james-page)]

Note we can whitelist the devices that OVS will probe which will improve this problem.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/667046

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/667046
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=3c66c48bbd11922aa4740e752dfdb5e4f35a959d
Submitter: Zuul
Branch: master

commit 3c66c48bbd11922aa4740e752dfdb5e4f35a959d
Author: James Page <email address hidden>
Date: Mon Jun 24 10:11:04 2019 +0100

    dpdk: misc fixes for EAL initialization

    For OpenStack Queens and later instances are setup with vhostuser
    ports in server mode, with the OVS side of the port connecting
    as a client to the vhostuser socket on disk; as a result we no
    longer need to pass permissions information via dpdk-extra (the
    two passed options are not valid in later OVS versions).

    In addition, we should also whitelist the devices we're going to
    use; this ensures that EAL initialization does not take an extended
    period of time reducing the amount of time taken to restart OVS.

    Change-Id: I224e778de0ed6e279b2de7f4f46781df33121165
    Closes-Bug: 1833734
    Closes-Bug: 1793729

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/19.04
Review: https://review.opendev.org/668635

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/668635
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-openvswitch/commit/?id=bd354841d5422f5d936c9f031228c3d5889368df
Submitter: Zuul
Branch: stable/19.04

commit bd354841d5422f5d936c9f031228c3d5889368df
Author: James Page <email address hidden>
Date: Mon Jun 24 10:11:04 2019 +0100

    dpdk: misc fixes for EAL initialization

    For OpenStack Queens and later instances are setup with vhostuser
    ports in server mode, with the OVS side of the port connecting
    as a client to the vhostuser socket on disk; as a result we no
    longer need to pass permissions information via dpdk-extra (the
    two passed options are not valid in later OVS versions).

    In addition, we should also whitelist the devices we're going to
    use; this ensures that EAL initialization does not take an extended
    period of time reducing the amount of time taken to restart OVS.

    Change-Id: I224e778de0ed6e279b2de7f4f46781df33121165
    Closes-Bug: 1833734
    Closes-Bug: 1793729
    (cherry picked from commit 3c66c48bbd11922aa4740e752dfdb5e4f35a959d)