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 A105F156 for ; Mon, 22 Jul 2013 14:57:20 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 22 Jul 2013 05:57:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.89,719,1367996400"; d="scan'208,217";a="349581850" Received: from orsmsx109.amr.corp.intel.com ([10.22.240.7]) by orsmga001.jf.intel.com with ESMTP; 22 Jul 2013 05:57:37 -0700 Received: from orsmsx105.amr.corp.intel.com ([169.254.4.145]) by ORSMSX109.amr.corp.intel.com ([169.254.2.244]) with mapi id 14.03.0123.003; Mon, 22 Jul 2013 05:57:37 -0700 From: "Gilmore, Walter E" To: "dev@dpdk.org" Thread-Topic: Re: [dpdk-dev] Any ideas how to stop DPDK from banning me from the Thread-Index: Ac6G2wlX8CkyJuWXT4yig+R53RyaZQ== Date: Mon, 22 Jul 2013 12:57:37 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.139] Content-Type: multipart/alternative; boundary="_000_DC16335EE7FE114791FFF955B21EDB4490112109ORSMSX105amrcor_" MIME-Version: 1.0 Subject: Re: [dpdk-dev] Any ideas how to stop DPDK from banning me from the 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, 22 Jul 2013 12:57:21 -0000 --_000_DC16335EE7FE114791FFF955B21EDB4490112109ORSMSX105amrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Antti, the current mechanism for scanning the PCIe devices is based on h= ow this project started. Initially the program was using a bare-metal envir= onment then progressed to the Linux userspace model. In the 1.4 release tha= t was just placed on the Intel IBL site we now have a script that unbinds t= he selected devices and binds them to the igb-uio driver then the Intel DPD= K will probe only the devices on the igb-uio. The black-list function can s= till be used since multiple Intel DPDK's can be run. In the 1.2.x release you can also modify the configuration file in /config/= defconfig_x86_64-default-linuxapp-gcc (if using 64bit gcc) and change the C= ONFIG_RTE_LIBRTE_IGB_PMD=3Dy line to CONFIG_RTE_LIBRTE_IGB_PMD=3Dn this wil= l stop the 1GbE devices from being scanned and unbound by the Intel DPDK pr= eventing you from losing connectivity over the 1GbE ports. Walt --_000_DC16335EE7FE114791FFF955B21EDB4490112109ORSMSX105amrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Antti, the current mechanism for scanning the PCIe device= s is based on how this project started. Initially the program was using a b= are-metal environment then progressed to the Linux userspace model. In the 1.4 release that was just placed on the = Intel IBL site we now have a script that unbinds the selected devices and b= inds them to the igb-uio driver then the Intel DPDK will probe only the dev= ices on the igb-uio. The black-list function can still be used since multiple Intel DPDK’s can be run. <= o:p>

 

In the 1.2.x release you can also modify the configuration f= ile in /config/defconfig_x86_64-default-linuxapp-gcc (if using 64bit gcc) a= nd change the CONFIG_RTE_LIBRTE_IGB_PMD=3Dy line to CONFIG_RTE_LIBRTE_IGB_PMD=3Dn this will stop the 1GbE devices from= being scanned and unbound by the Intel DPDK preventing you from losing con= nectivity over the 1GbE ports.

 

Walt

--_000_DC16335EE7FE114791FFF955B21EDB4490112109ORSMSX105amrcor_--