Following various issues seen in deployments that involved mlx5 devices,
here is a proposal to disable DPDK initial device probing.

Changing this as the default behavior should be fine as OVS relies on
hotplugs for many years now.
But in case something gets broken, keep an option to restore the
original behavior.

As for what to expect on DPDK side in the future, the new option
has been merged in preparation of v26.07-rc1.
See: https://git.dpdk.org/dpdk/commit/?id=7baf81674a01


-- 
David Marchand

Changes since v1:
- improved documentation wording and references,
- avoided allocating memory for error strings in patch 1,
- added checks for --allow/--block and --no-pci options in patch 2,

Changes since RFC v2:
- updated descriptions and comments as Eelco suggested,

Changes since RFC v1:
- adjusted logs in patch 1,
- handled other DPDK buses in patch 2,


David Marchand (2):
  netdev-dpdk: Enhance logging for port hotplug.
  dpdk: Disable initial device probe.

 Documentation/howto/dpdk.rst         |  6 +++++
 Documentation/intro/install/dpdk.rst |  6 +++++
 NEWS                                 |  5 ++++
 lib/dpdk.c                           | 31 +++++++++++++++++++++
 lib/netdev-dpdk.c                    | 22 ++++++++++-----
 tests/system-dpdk-macros.at          |  2 +-
 tests/system-dpdk.at                 | 40 ++++++++++++++--------------
 vswitchd/vswitch.xml                 | 31 +++++++++++++++++++++
 8 files changed, 116 insertions(+), 27 deletions(-)

-- 
2.53.0

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to