[dpdk-dev] [RFC PATCH 0/6] Restructure EAL device model for bus support

Thomas Monjalon thomas.monjalon at 6wind.com
Mon Nov 21 10:08:32 CET 2016

2016-11-20 16:30, David Marchand:
> For a first patchset, I would see:
> - introduce the rte_bus object. In rte_eal_init, for each bus, we call
> the scan method. Then, for each bus, we find the appropriate
> rte_driver using the bus match method then call the probe method. If
> the probe succeeds, the rte_device points to the associated
> rte_driver,
> - migrate the pci scan code to a pci bus (scan looks at sysfs for
> linux / ioctl for bsd + devargs for blacklist / whitelist ?), match is
> the same at what is done in rte_eal_pci_probe_one_driver() at the
> moment,
> - migrate the vdev init code to a vdev bus (scan looks at devargs):
> this is new, we must create rte_device objects for vdev drivers to use
> later

I think it can be 3 patchsets.
Who can work on the vdev part please?

> Then we can talk about the next steps once the bus is in place.


More information about the dev mailing list