From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by dpdk.org (Postfix) with ESMTP id 78DC48E5F for ; Fri, 11 Dec 2015 12:28:12 +0100 (CET) Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.15.2/8.15.2) with ESMTPS id tBBBSC2O006940 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 11 Dec 2015 11:28:12 GMT Received: from SGSIHTC002.nsn-intra.net ([10.159.225.19]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id tBBBRknL002665 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 11 Dec 2015 12:28:11 +0100 Received: from SGSIHTC007.nsn-intra.net (10.159.225.24) by SGSIHTC002.nsn-intra.net (10.159.225.19) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 11 Dec 2015 19:27:45 +0800 Received: from SGSIMBX011.nsn-intra.net ([169.254.11.161]) by SGSIHTC007.nsn-intra.net ([10.159.225.24]) with mapi id 14.03.0248.002; Fri, 11 Dec 2015 19:27:45 +0800 From: "P D, Arun (Nokia - IN/Bangalore)" To: "EXT Pattan, Reshma" Thread-Topic: Issue on Running KNI application Thread-Index: AdEx4w8Z+m5WiwS1Tjilu9ZZyxI9XwAIZ9+gAA5iCnAADaFCIABjJD3w Date: Fri, 11 Dec 2015 11:27:44 +0000 Message-ID: <452B978F8CA9744BAA81E3E69370ABC4D92DD3@SGSIMBX011.nsn-intra.net> References: <452B978F8CA9744BAA81E3E69370ABC4D92C14@SGSIMBX011.nsn-intra.net> <3AEA2BF9852C6F48A459DA490692831FF8AB00@IRSMSX109.ger.corp.intel.com> <452B978F8CA9744BAA81E3E69370ABC4D92C4B@SGSIMBX011.nsn-intra.net> <3AEA2BF9852C6F48A459DA490692831FF8B557@IRSMSX109.ger.corp.intel.com> In-Reply-To: <3AEA2BF9852C6F48A459DA490692831FF8B557@IRSMSX109.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.159.225.125] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: clean X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate-size: 5573 X-purgate-ID: 151667::1449833292-000062B2-3C49D4DC/0/0 Cc: "users@dpdk.org" Subject: Re: [dpdk-users] Issue on Running KNI application X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Dec 2015 11:28:12 -0000 Thanks for your inputs. Regards, Arun Raj -----Original Message----- From: EXT Pattan, Reshma [mailto:reshma.pattan@intel.com]=20 Sent: Wednesday, December 09, 2015 5:12 PM To: P D, Arun (Nokia - IN/Bangalore) Cc: users@dpdk.org Subject: RE: Issue on Running KNI application Hi Arun, I see below EAL info from the given output, that means you have only 4 lcor= es on your board numbering 0, 1,2,3. So you need to change the core mask and core numbering that you have passed= to --config. > EAL: Detected 4 lcore(s) > EAL: lcore 4 unavailable Ex: if you want to use all 4 cores u need to try below command ./kni -c 0xf -n 4 -- -P -p 0x3 --config=3D"(0,1,0),(1,2,3)" -c 0xf =3D=3D> enables all 4 cores 0,1,2,3 --config=3D"(0,1,0),(1,2,3)" =3D=3D>(0,1,0) core 1 is RX core and core 0 i= s TX core =3D=3D>(1,2,3) core 2 is RX core and core 3 is TX core You can change RX and TX core numbers to your choice, I just gave an examp= le.=20 But whatever cores you wants to use make sure those exists on board and sho= uld be enabled in core mask and the same should be used in config option. You can check how many lcores are there on your board by using ./too/cpu_la= yout.py To check how to run KNI and understand command line options take a look at= KNI sample application section from Sample Application User guide. Thanks, Reshma > -----Original Message----- > From: P D, Arun (Nokia - IN/Bangalore) [mailto:arun.p_d@nokia.com] > Sent: Wednesday, December 9, 2015 5:49 AM > To: Pattan, Reshma > Cc: users@dpdk.org > Subject: RE: Issue on Running KNI application >=20 > Hi Reshma, >=20 > I am getting error, upon executing saying that it's an invalid core mask. >=20 > Also please let me know how you are calculating the hexadecimal bitmask f= or > the cores. >=20 > ./kni -c 0x1E -n 4 -- -P -p 0x3 --config=3D"(0,1,3),(1,2,4)" >=20 > EAL: Detected lcore 0 as core 0 on socket 0 > EAL: Detected lcore 1 as core 1 on socket 0 > EAL: Detected lcore 2 as core 2 on socket 0 > EAL: Detected lcore 3 as core 3 on socket 0 > EAL: Support maximum 128 logical core(s) by configuration. > EAL: Detected 4 lcore(s) > EAL: lcore 4 unavailable > EAL: invalid coremask >=20 > Regards, > Arun Raj >=20 > -----Original Message----- > From: EXT Pattan, Reshma [mailto:reshma.pattan@intel.com] > Sent: Wednesday, December 09, 2015 3:37 AM > To: P D, Arun (Nokia - IN/Bangalore) ; users@dpdk.org > Subject: RE: Issue on Running KNI application >=20 > Hi Arun, >=20 > Core mask value i.e. -c value should be 0x1E in your command. Because you= are > using cores 1,2,3,4 so their respective bits must be set to 1 in -c value= . >=20 > ./kni -c 0x1E -n 4 -- -P -p 0x3 --config=3D"(0,1,3),(1,2,4)" >=20 > Thanks, > Reshma >=20 > > -----Original Message----- > > From: users [mailto:users-bounces@dpdk.org] On Behalf Of P D, Arun > > (Nokia - > > IN/Bangalore) > > Sent: Tuesday, December 8, 2015 6:06 PM > > To: users@dpdk.org > > Subject: [dpdk-users] Issue on Running KNI application > > > > Hello, > > > > I am trying to run the KNI program in examples of dpdk. > > > > I am giving the following command and facing the error as "Cause: > > lcore id 1 for port 0 receiving not enabled". > > > > Please let me know if I am making any mistake at config parameters, or > > I am missing something. > > > > ./kni -c 4 -n 4 -- -P -p 0x3 --config=3D"(0,1,3),(1,2,4)" > > > > EAL: Detected lcore 0 as core 0 on socket 0 > > EAL: Detected lcore 1 as core 1 on socket 0 > > EAL: Detected lcore 2 as core 2 on socket 0 > > EAL: Detected lcore 3 as core 3 on socket 0 > > EAL: Support maximum 128 logical core(s) by configuration. > > EAL: Detected 4 lcore(s) > > EAL: Setting up physically contiguous memory... > > EAL: Ask a virtual area of 0x200000 bytes > > EAL: Virtual area found at 0x7fd603600000 (size =3D 0x200000) > > EAL: Ask a virtual area of 0x1000000 bytes > > EAL: Virtual area found at 0x7fd602400000 (size =3D 0x1000000) > > EAL: Ask a virtual area of 0x3c00000 bytes > > EAL: Virtual area found at 0x7fd5fe600000 (size =3D 0x3c00000) > > EAL: Ask a virtual area of 0x50400000 bytes > > EAL: Virtual area found at 0x7fd5ae000000 (size =3D 0x50400000) > > EAL: Ask a virtual area of 0x29c00000 bytes > > EAL: Virtual area found at 0x7fd584200000 (size =3D 0x29c00000) > > EAL: Ask a virtual area of 0x1000000 bytes > > EAL: Virtual area found at 0x7fd583000000 (size =3D 0x1000000) > > EAL: Ask a virtual area of 0x200000 bytes > > EAL: Virtual area found at 0x7fd582c00000 (size =3D 0x200000) > > EAL: Requesting 1024 pages of size 2MB from socket 0 > > EAL: TSC frequency is ~3192614 KHz > > EAL: Master lcore 2 is ready (tid=3D3cb98e0;cpuset=3D[2]) > > EAL: PCI device 0000:03:00.0 on NUMA socket -1 > > EAL: probe driver: 8086:1533 rte_igb_pmd > > EAL: Not managed by a supported kernel driver, skipped > > EAL: PCI device 0000:05:00.0 on NUMA socket -1 > > EAL: probe driver: 8086:100e rte_em_pmd > > EAL: Not managed by a supported kernel driver, skipped > > EAL: PCI device 0000:06:00.0 on NUMA socket -1 > > EAL: probe driver: 8086:10d3 rte_em_pmd > > EAL: Not managed by a supported kernel driver, skipped > > APP: Port ID: 0 > > APP: Rx lcore ID: 1, Tx lcore ID: 3 > > APP: Port ID: 1 > > APP: Rx lcore ID: 2, Tx lcore ID: 4 > > EAL: Error - exiting with code: 1 > > Cause: lcore id 1 for port 0 receiving not enabled > > > > Regards, > > Arun Raj