From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 0/4] Introduce net bus Date: Thu, 08 Jun 2017 09:31:23 +0200 Message-ID: <34816509.TmcHNXKEUC@xps> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Ferruh Yigit To: Gaetan Rivet Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id A001A2BB9 for ; Thu, 8 Jun 2017 09:31:24 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 08/06/2017 02:00, Gaetan Rivet: > This new bus takes as devices kernel netdevices. > It offers an API for drivers to register a translation layer that would > transform the netdev name to one their regular PMD would be able to > probe. > > This is PoC. It currently only works for MLX4 and MLX5 PMDs as they were > bifurcated and had very little work to do otherwise. > > The planned feature is for at least all PCI drivers, be able to unbind > the device from its kmod and bind it to a choosen IO module, prior to > probing. > > Additional possible feature would be a close integration with eventually > NCI-like lib, to transparently capture kernel devices, keep a control > interface present and bind / unbind the underlying hardware function as > necessary. I'm sorry, I do not understand the description. Please start with a real problem statement and explain how it is solved. Thanks