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:13:54 +0200
Message-ID: <21769641.JDxLthIqDH@xps>
References: <20180405191305.26813-1-sthemmin@microsoft.com>
 <1607753.vleKbttEpa@xps> <20180405140329.3595edb8@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
To: Stephen Hemminger <sthemmin@microsoft.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 F1F5A1CDEC
 for <dev@dpdk.org>; Thu,  5 Apr 2018 23:13:55 +0200 (CEST)
In-Reply-To: <20180405140329.3595edb8@xeon-e3>
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:03, Stephen Hemminger:
> On Thu, 05 Apr 2018 22:43:39 +0200
> Thomas Monjalon <thomas@monjalon.net> 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).
> > 
> > In order to make this change happen, we should not
> > add this hv_uio_setup.sh script.
> 
> Yes, this is a temporary script like dpdk-bind, want to get rid of it
> and do everything inside driver. That is the next step.

If this is temporary, it is a step in the wrong direction which
could confuse users.

If it becomes definitive (design discussion in progress), then it should
be merged in dpdk-devbind.py.