From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id C0C2E1CDD8 for ; Thu, 5 Apr 2018 23:10:34 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5B620212FB; Thu, 5 Apr 2018 17:10:34 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 05 Apr 2018 17:10:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=Xerbvq1omk4LlhBOJhg+WJD2Gu SzmojBrs/QEAPId3M=; b=hQTHxZiWNUph0K86KOnoekLDT0uTb+FdW3ZEG9FLTM 16r5n7tzRo7vsijYS7+EMdXzj8b24rIh09spJn/B5gub3X2PS3sIW+XBD/dhWFtO KRGc3zh8gc1k49IvjftLC7Zwr+ERhpFBxSVGFRuAhGBz150uxKefr6RXQAx93LM0 o= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Xerbvq 1omk4LlhBOJhg+WJD2GuSzmojBrs/QEAPId3M=; b=GDOP1RcDbuBq3/uh8k0iCm e9XzgQ0C2Kk4sSEDlj+nP7/08zpLRP1AvoaDaUwR3TWVaqixwCC1bC7Esq60O5Ls QUf+0JuLKGF/Mgmg3xVp92Dfk0tfVvWPisIF+EKYbCuFpMyLomKsbueLX6pt+IA8 yYWsv5cKtTGp2gstgCD5FmY3F8qNkM8axDHJyn/nLbyf27Wo/WSZ18Yj0Z5KrlK4 BmJE8hUl0BRTr6PsChx1296ey2x4Ynq995X1usNTuKbUkyPYuoSVRBlWeCnaE3/v 7IKxEdDFB/Uo+yGS/169wyWFS1UvxEB/aVHD29Ll4YeJKioKOmUGeIPY9IcVz+KQ == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id AD9ADE4449; Thu, 5 Apr 2018 17:10:33 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson Cc: Stephen Hemminger , dev@dpdk.org, Stephen Hemminger Date: Thu, 05 Apr 2018 23:10:33 +0200 Message-ID: <1792191.Hreas2QKXW@xps> In-Reply-To: <20180405210734.GA85168@bricha3-MOBL.ger.corp.intel.com> References: <20180405191305.26813-1-sthemmin@microsoft.com> <1607753.vleKbttEpa@xps> <20180405210734.GA85168@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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:10:35 -0000 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.