[dpdk-dev] [PATCH v7 00/22] Device querying
Thomas Monjalon
thomas at monjalon.net
Mon Apr 23 00:54:54 CEST 2018
15/04/2018 17:07, Gaetan Rivet:
> This patchset introduces a new EAL API for querying devices,
> filtered by arbitrary properties.
>
> The following elements are introduced to this end:
>
> * A new object, "rte_class", is used to describe
> the device class abstraction layer (eth, crypto, ...).
>
> * Both rte_bus and rte_class now offer a way to
> list their devices and filter the result
> using locally defined properties.
>
> * The rte_dev API now has an rte_dev_iterator, which
> is the way for the user to define the device filter
> and iterate upon the resulting set.
>
> As an example, the "eth" device class is implemented.
>
> Additionally, the device filters for
>
> + rte_bus_pci
> + rte_bus_vdev
> + rte_class_eth
>
> are implemented and can be used with some
> properties each, to show how to extend those.
>
> Some example of filters:
>
> "bus=pci/class=eth"
> "bus=pci"
> "class=eth"
> "class=eth,name=net_ring0"
> "bus=pci,id=00:00.0"
> "bus=vdev,driver=net_ring"
Thanks for the very big work Gaetan.
This series has some cleanups, fixes, and more importantly,
introduces the framework for a generic device syntax.
I am not clear what is missing in the properties parsing?
In various buses and classes implementations?
Are we close of the next step, revisiting -w/-b and --vdev options?
More information about the dev
mailing list