From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tan, Jianfeng" Subject: Re: [PATCH] bus/vdev: add custom scan hook Date: Fri, 1 Dec 2017 13:48:06 +0800 Message-ID: <8fc8dcb8-c32b-8ec4-8762-b2f2bba09c5c@intel.com> References: <20171201003642.19827-1-thomas@monjalon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id F266F29D9 for ; Fri, 1 Dec 2017 06:48:09 +0100 (CET) In-Reply-To: <20171201003642.19827-1-thomas@monjalon.net> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 > --- > warning: to be tested > --- > drivers/bus/vdev/rte_bus_vdev.h | 29 ++++++++++++++++ > drivers/bus/vdev/vdev.c | 75 +++++++++++++++++++++++++++++++++++++++++ > 2 files changed, 104 insertions(+) [...]