From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 2/3] usertools: add hv_uio_setup script
Date: Thu, 05 Apr 2018 23:10:33 +0200
Message-ID: <1792191.Hreas2QKXW@xps>
References: <20180405191305.26813-1-sthemmin@microsoft.com>
 <1607753.vleKbttEpa@xps>
 <20180405210734.GA85168@bricha3-MOBL.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: Stephen Hemminger <sthemmin@microsoft.com>, dev@dpdk.org,
 Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com
 [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id C0C2E1CDD8
 for <dev@dpdk.org>; Thu,  5 Apr 2018 23:10:34 +0200 (CEST)
In-Reply-To: <20180405210734.GA85168@bricha3-MOBL.ger.corp.intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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.