From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH 2/3] usertools: add hv_uio_setup script Date: Thu, 5 Apr 2018 22:07:34 +0100 Message-ID: <20180405210734.GA85168@bricha3-MOBL.ger.corp.intel.com> References: <20180405191305.26813-1-sthemmin@microsoft.com> <20180405191305.26813-3-sthemmin@microsoft.com> <1607753.vleKbttEpa@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Stephen Hemminger , dev@dpdk.org, Stephen Hemminger To: Thomas Monjalon Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id A30D41CDA5 for ; Thu, 5 Apr 2018 23:08:04 +0200 (CEST) Content-Disposition: inline In-Reply-To: <1607753.vleKbttEpa@xps> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Apr 05, 2018 at 10:43:39PM +0200, Thomas Monjalon wrote: > 05/04/2018 21:13, Stephen Hemminger: > > Small script to rebind netvsc kernel device to Hyper-V > > networking PMD. It could be integrated in dpdk-bind, but dpdk-bind > > is focused on PCI, and that would get messy. > > > > Eventually, this functionality will be built into netvsc driver > > (see vdev_netvsc as an example). > > I believe we should avoid creating such script. > The direction to go, for hotplug, is to remove dpdk-devbind.py, > and implement kernel binding in PMDs (with EAL helpers). > I'm not convinced at all that that is the direction to go. I instead would prefer to see all binding happen outside DPDK. I believe having udev or similar manage bindings, set up via e.g driverctl[1], is a far better path. Just my 2c. /Bruce [1] https://gitlab.com/driverctl/driverctl