Hi Thomas, Please help us to understand why we need this.
On 12/1/2017 8:36 AM, Thomas Monjalon wrote:
The scan callback allows to spawn a vdev automatically given some custom scan rules.
These two new APIs (rte_vdev_add_custom_scan and rte_vdev_remove_custom_scan) are called by applications? If so, why not just constructing them in the parameters before passing to rte_eal_init?
It is especially useful to create a TAP device automatically connected to a netdevice as remote.
It sounds like an use case. Without this patch, I suppose we can already do this?
Thanks, Jianfeng
Signed-off-by: Thomas Monjalon <tho...@monjalon.net> --- warning: to be tested --- drivers/bus/vdev/rte_bus_vdev.h | 29 ++++++++++++++++ drivers/bus/vdev/vdev.c | 75 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 104 insertions(+)
[...]
