On Thu, Feb 26, 2026 at 05:20:56PM +0100, David Marchand wrote: > Some applications use port hotplug as their primary way for using DPDK > resources. > Having a systematic device probing is a problem when not all available > resources will be used by the application, as such applications won't set > an explicit allow list at startup. > > This is the case for OVS on systems with multiple mlx5 devices: > one device can be used by the kernel while the other(s) are used by DPDK. > In such a setup, the kernel used device may get reconfigured in > unexpected ways and trigger issues like the one described by Kevin > not so long ago in bugzilla 1873. > > Add an EAL option so that we can change the default behavior from > block-listing to allow-listing. > > Signed-off-by: David Marchand <[email protected]> > --- > Changes since RFC v1: > - changed approach following Bruce suggestion, Acked-by: Bruce Richardson <[email protected]>
- [RFC v2 1/5] devtools: check packet forwarding in null t... David Marchand
- Re: [RFC v2 1/5] devtools: check packet forwarding ... Bruce Richardson
- [RFC v2 3/5] drivers/bus: require probe function for NXP... David Marchand
- Re: [RFC v2 3/5] drivers/bus: require probe functio... Bruce Richardson
- [RFC v2 2/5] bus/fslmc: fix bus cleanup David Marchand
- [RFC v2 4/5] bus: factorize device selection David Marchand
- Re: [RFC v2 4/5] bus: factorize device selection Bruce Richardson
- Re: [RFC v2 4/5] bus: factorize device selectio... David Marchand
- Re: [RFC v2 4/5] bus: factorize device sele... Bruce Richardson
- [RFC v2 5/5] eal: configure initial device probing David Marchand
- Re: [RFC v2 5/5] eal: configure initial device prob... Bruce Richardson
- Re: [RFC v2 5/5] eal: configure initial device prob... Robin Jarry
- Re: [RFC v2 5/5] eal: configure initial device ... Thomas Monjalon
- Re: [RFC v2 5/5] eal: configure initial dev... Bruce Richardson
- Re: [RFC v2 5/5] eal: configure initial... Stephen Hemminger

