From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 403681CDB3 for ; Fri, 6 Apr 2018 01:57:50 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Apr 2018 16:57:49 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,413,1517904000"; d="scan'208";a="31957010" Received: from irsmsx152.ger.corp.intel.com ([163.33.192.66]) by orsmga006.jf.intel.com with ESMTP; 05 Apr 2018 16:57:48 -0700 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.216]) by IRSMSX152.ger.corp.intel.com ([169.254.6.253]) with mapi id 14.03.0319.002; Fri, 6 Apr 2018 00:57:47 +0100 From: "Ananyev, Konstantin" To: Thomas Monjalon , "Richardson, Bruce" CC: Stephen Hemminger , "dev@dpdk.org" , Stephen Hemminger Thread-Topic: [dpdk-dev] [PATCH 2/3] usertools: add hv_uio_setup script Thread-Index: AQHTzRIyX0dLDrI1iUu+sKtjaxojBaPykqWAgAAGrwCAAADVgIAAPSBg Date: Thu, 5 Apr 2018 23:57:47 +0000 Message-ID: <2601191342CEEE43887BDE71AB977258A0AB9CCD@irsmsx105.ger.corp.intel.com> References: <20180405191305.26813-1-sthemmin@microsoft.com> <1607753.vleKbttEpa@xps> <20180405210734.GA85168@bricha3-MOBL.ger.corp.intel.com> <1792191.Hreas2QKXW@xps> In-Reply-To: <1792191.Hreas2QKXW@xps> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOWI5YWRlMWMtOTk2Ni00MDE4LWFmMTItYmY0OTY2ZDg5Y2MwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImNJZ2VRVTlNaVg3U1hyQnNcL3VkamZXSTJpb1JJcjRuQ3dubTRCSEI0Rnl3PSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 23:57:52 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Thursday, April 5, 2018 10:11 PM > To: Richardson, Bruce > Cc: Stephen Hemminger ; dev@dpdk.org; Stephen Hem= minger > Subject: Re: [dpdk-dev] [PATCH 2/3] usertools: add hv_uio_setup script >=20 > 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 wo= uld > > 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 p= ath. >=20 > This is a system admin tool, and only for Linux. > Having the binding logic inside DPDK, allows the application to control > how hotplug behave. I also don't think that DPDK application should control hotplug behavior lo= gic. It is clearly up to the system admin to make such decisions.=20 Konstantin