Hi Thomas, On Thu, Jun 08, 2017 at 09:31:23AM +0200, Thomas Monjalon wrote: > I'm sorry, I do not understand the description. > Please start with a real problem statement and explain how it is solved. > Thanks
Sure. Currently, we probe devices by using ./usertools/dpkd-devbind.py -b igb_uio 00:02.0 ./build/app/whatever -w 00:02.0 ./usertools/dpkd-devbind.py -b ixgbe 00:02.0 Wouldn't it be nice to be able to: ./build/app/whatever -w ens2 Instead? Many things are missing for this. This PoC only shows the simplest case with a bifurcated driver, but the concept is there. This bus is an intepretation layer to transform a kernel netdevice name into a usable DPDK device, which should give enough info about its dependencies: bus, IO module, resource management policies, etc... to prepare it. I plan to add binding / unbinding afterward, and I wanted to propose this early enough as there were talks of kernel control plane, and this could be a building block to this general direction. Auto-unbind assumes a clean exit from the DPDK application. This might be a big departure from current assumptions, where buses very seldom plan for ending operations. i.e. rte_bus has scan and probe, but no remove API. While unplug should soon exist, this is a crude workaround. -- Gaëtan Rivet 6WIND
