[dpdk-dev] kernel binding of devices + hotplug

Flavio Leitner fbl at redhat.com
Wed Apr 18 20:54:11 CEST 2018


On Wed, Apr 18, 2018 at 11:17:47AM -0700, Stephen Hemminger wrote:
> On Wed, 18 Apr 2018 11:11:01 -0300
> Flavio Leitner <fbl at redhat.com> wrote:
> 
> > On Sun, Apr 15, 2018 at 01:48:36AM +0000, Stephen Hemminger wrote:
> > > My vote is to work with udev and not try to replace it.
> > > 
> > > Driverctl works well. Just not for bifurcated driver  
> > 
> > I second that.  We also have other system configs to care about like
> > kernel parameters and hugepage configuration which I think follow the
> > same idea that they are system wide configs and should not be managed
> > by DPDK itself.
> 
> Maybe teach driverctl (and udev) to handle bifurcated drivers.

I don't know the challenges to tech driverctl to handle bifurcated
drivers but I would agree that it should be our first place to look at.

> Unfortunately, vendors are very fractured on how network devices are managed.

You mean distros? hw vendors? all vendors? :)

Perhaps if community focus on something, then they might follow at some
point.

-- 
Flavio


More information about the dev mailing list