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 6A877AF89 for ; Mon, 14 Apr 2014 17:41:02 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 14 Apr 2014 08:41:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,857,1389772800"; d="scan'208";a="492663576" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by orsmga001.jf.intel.com with ESMTP; 14 Apr 2014 08:41:00 -0700 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.224]) by IRSMSX103.ger.corp.intel.com ([163.33.3.157]) with mapi id 14.03.0123.003; Mon, 14 Apr 2014 16:40:59 +0100 From: "Burakov, Anatoly" To: Stephen Hemminger Thread-Topic: [dpdk-dev] IGB_UIO port unbinding Thread-Index: Ac9Un4qoqrlS9BlDSTS8n+CPSzCJ7gA+ppGAAIknFVAAC+v8gAACNijA Date: Mon, 14 Apr 2014 15:40:59 +0000 Message-ID: References: <20140411092435.29e06974@nehalam.linuxnetplumber.net> <20140414083303.09cb43ed@nehalam.linuxnetplumber.net> In-Reply-To: <20140414083303.09cb43ed@nehalam.linuxnetplumber.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] IGB_UIO port unbinding X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2014 15:41:02 -0000 Hi Stephen, =20 > The problem is that doing the initialization requires duplicating all the= logic to > probe the PCI bus and do blacklisting etc in the startup application. Not quite sure what you're referring to here, could you please elaborate a = bit more? If you mean the EAL PCI probing and blacklisting/whitelisting, th= en yes - we have to do it, but this is out of necessity more than anything = else - there's no way around that since DPDK is using userspace drivers. DP= DK doesn't require to bind/unbind kernel drivers in the EAL however - there= is already a way to do that that doesn't involve EAL-side logic. EAL simpl= y checks if a particular PCI device is bound to a certain driver and if it'= s blacklisted (in other words, EAL checks if it is able to use the device, = but doesn't try to modify the environment). Best regards, Anatoly Burakov DPDK SW Engineer -------------------------------------------------------------- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare