From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id A2FA3595D for ; Mon, 14 Apr 2014 10:58:55 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 14 Apr 2014 01:54:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,856,1389772800"; d="scan'208";a="520338585" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by orsmga002.jf.intel.com with ESMTP; 14 Apr 2014 01:58:06 -0700 Received: from irsmsx154.ger.corp.intel.com (163.33.192.96) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 14 Apr 2014 09:57:54 +0100 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.224]) by IRSMSX154.ger.corp.intel.com ([163.33.192.96]) with mapi id 14.03.0123.003; Mon, 14 Apr 2014 09:57:54 +0100 From: "Burakov, Anatoly" To: Stephen Hemminger Thread-Topic: [dpdk-dev] IGB_UIO port unbinding Thread-Index: Ac9Un4qoqrlS9BlDSTS8n+CPSzCJ7gA+ppGAAIknFVA= Date: Mon, 14 Apr 2014 08:57:54 +0000 Message-ID: References: <20140411092435.29e06974@nehalam.linuxnetplumber.net> In-Reply-To: <20140411092435.29e06974@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 08:58:56 -0000 Hi Stephen, > I actually liked the unbind code that was there. It meant that additional= logic > did not have to be added to the startup script to do PCI discovery and > finding/mapping devices. >=20 > As it is the EAL startup process is a bit of a mess. It assumes that vari= ous bits > of information and infrastructure are already in place prior to starting = the > DPDK application. I would argue that it's not the responsibility of the application to set up= its environment. The EAL startup process is indeed a bit all over the plac= e, but the alternative would be worse. Those "various bits of information a= nd infrastructure" you're referring to include, say, hugepages - I don't th= ink it's a good idea for an application to meddle with system's hugepages a= ny more than I think it's a good idea for it to meddle with the driver bind= ings. Plus, current state of affairs makes for headaches in the future when suppo= rt for other drivers is implemented (say, VFIO). It's much better to move t= he responsibility of binding the drivers to the user, and DPDK provides qui= te convenient means to do that (the PCI binding Python script) and also a c= entralized script to prepare the DPDK environment without much hassle (the = setup.sh). 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