From mboxrd@z Thu Jan 1 00:00:00 1970 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) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Apr 2018 14:07:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,412,1517904000"; d="scan'208";a="34684141" Received: from akanter-mobl1.ger.corp.intel.com ([10.252.21.137]) by fmsmga002.fm.intel.com with SMTP; 05 Apr 2018 14:07:36 -0700 Received: by (sSMTP sendmail emulation); Thu, 05 Apr 2018 22:07:35 +0100 Date: Thu, 5 Apr 2018 22:07:34 +0100 From: Bruce Richardson To: Thomas Monjalon Cc: Stephen Hemminger , dev@dpdk.org, Stephen Hemminger 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 Content-Disposition: inline In-Reply-To: <1607753.vleKbttEpa@xps> Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [PATCH 2/3] usertools: add hv_uio_setup script X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Apr 2018 21:08:05 -0000 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