From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH 2/3] usertools: add hv_uio_setup script Date: Thu, 5 Apr 2018 15:43:08 -0700 Message-ID: <20180405154308.00a5a64a@xeon-e3> References: <20180405191305.26813-1-sthemmin@microsoft.com> <1607753.vleKbttEpa@xps> <20180405210734.GA85168@bricha3-MOBL.ger.corp.intel.com> <1792191.Hreas2QKXW@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Bruce Richardson , Stephen Hemminger , dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-pl0-f66.google.com (mail-pl0-f66.google.com [209.85.160.66]) by dpdk.org (Postfix) with ESMTP id AB5511CDEB for ; Fri, 6 Apr 2018 00:43:10 +0200 (CEST) Received: by mail-pl0-f66.google.com with SMTP id v5-v6so19373020plo.4 for ; Thu, 05 Apr 2018 15:43:10 -0700 (PDT) In-Reply-To: <1792191.Hreas2QKXW@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, 05 Apr 2018 23:10:33 +0200 Thomas Monjalon wrote: > 05/04/2018 23:07, Bruce Richardson: > > 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. > > This is a system admin tool, and only for Linux. > Having the binding logic inside DPDK, allows the application to control > how hotplug behave. > > What about using driverctl? That solution would work for both PCI and VMBUS, but not sure how widely adopted it is by distributions.