[dpdk-dev] kernel binding of devices + hotplug

Stephen Hemminger stephen at networkplumber.org
Mon Apr 16 18:57:23 CEST 2018


On Mon, 16 Apr 2018 16:11:12 +0000
Matan Azrad <matan at mellanox.com> wrote:

> > If the device management is only managed in one place, i.e. not in DPDK,
> > then there is no conflict to manage.  
> 
> I can't agree with this statement,
> The essence of DPDK is to give a good alternative to managing network devices,
> DPDK actually takes a lot of management area to manage by itself to do the user life better :)

More is not better! DPDK is poorly integrated into Linux overall system. Doing
more in DPDK makes this worse not better.

Buried under this discussion is the fact that the Mellanox bifurcated driver
behaves completely differently from every other driver. This makes coming to
a common solution much harder. The bifurcated model has advantages and disadvantages,
in this case it is a disadvantage since it is not easy to manage usage when
it is a shared resource.



More information about the dev mailing list