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 14:18:12 -0700 Message-ID: <20180405141812.3e2e619d@xeon-e3> References: <20180405191305.26813-1-sthemmin@microsoft.com> <1607753.vleKbttEpa@xps> <20180405140329.3595edb8@xeon-e3> <21769641.JDxLthIqDH@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Stephen Hemminger , dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-pl0-f68.google.com (mail-pl0-f68.google.com [209.85.160.68]) by dpdk.org (Postfix) with ESMTP id C59F21CDC2 for ; Thu, 5 Apr 2018 23:18:14 +0200 (CEST) Received: by mail-pl0-f68.google.com with SMTP id s24-v6so21047227plq.6 for ; Thu, 05 Apr 2018 14:18:14 -0700 (PDT) In-Reply-To: <21769641.JDxLthIqDH@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:13:54 +0200 Thomas Monjalon wrote: > 05/04/2018 23:03, Stephen Hemminger: > > On Thu, 05 Apr 2018 22:43:39 +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). > > > > > > 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. > > This is an experimental driver, if everyone waits until everything is done there would be no review or testing.