From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 5CC342956 for ; Wed, 6 Apr 2016 11:22:06 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP; 06 Apr 2016 02:22:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,447,1455004800"; d="scan'208";a="681651076" Received: from irsmsx109.ger.corp.intel.com ([163.33.3.23]) by FMSMGA003.fm.intel.com with ESMTP; 06 Apr 2016 02:22:04 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.239]) by IRSMSX109.ger.corp.intel.com ([169.254.13.174]) with mapi id 14.03.0248.002; Wed, 6 Apr 2016 10:22:03 +0100 From: "Singh, Jasvinder" To: "Talukdar, Biju" , users Thread-Topic: problem running ip pipeline application Thread-Index: AQHRj5yVBfb1XFGsT0mpdZvI+6Lsnp98ntDw Date: Wed, 6 Apr 2016 09:22:03 +0000 Message-ID: <54CBAA185211B4429112C315DA58FF6DDED8FD@IRSMSX103.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOTA5ZDBkNjEtZTgxYy00YTVlLWI3NzUtMThmMjhjYjNkYTVlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX1BVQkxJQyJ9XX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNS45LjYuNiIsIlRydXN0ZWRMYWJlbEhhc2giOiJMcGxzbWl3ZUVWXC9DbEpoNm9XTlwvaGE0cithY2V0VlFRXC9YcnBQcVI2YVwvND0ifQ== x-ctpclassification: CTP_PUBLIC x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] problem running ip pipeline 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: Wed, 06 Apr 2016 09:22:07 -0000 Hi, > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Talukdar, Biju > Sent: Wednesday, April 6, 2016 1:43 AM > To: users > Cc: Talukdar, Biju > Subject: [dpdk-users] problem running ip pipeline application >=20 > Hi , >=20 >=20 > I am getting the following error when trying to run dpdk ip pipeline > example.Could someone please tell me what went wrong. >=20 >=20 > system configuration: >=20 > dpdk 2.2.0 >=20 > ubuntu 14.04 >=20 >=20 > network driver: >=20 > /dpdk-2.2.0$ ./tools/dpdk_nic_bind.py --status >=20 > Network devices using DPDK-compatible driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:04:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=3Digb_u= io > unused=3D >=20 > Network devices using kernel driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:04:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=3Deth3 > drv=3Dixgbe unused=3Digb_uio > 0000:05:00.0 'I350 Gigabit Network Connection' if=3Deth0 drv=3Digb > unused=3Digb_uio *Active* > 0000:05:00.1 'I350 Gigabit Network Connection' if=3Deth2 drv=3Digb > unused=3Digb_uio >=20 > Other network devices > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:03:00.0 'Device 15ad' unused=3Digb_uio > 0000:03:00.1 'Device 15ad' unused=3Digb_uio uml@uml:~/dpdk-2.2.0$ > ./tools/dpdk_nic_bind.py --status >=20 > Network devices using DPDK-compatible driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:04:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=3Digb_u= io > unused=3D >=20 > Network devices using kernel driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:04:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=3Deth3 > drv=3Dixgbe unused=3Digb_uio > 0000:05:00.0 'I350 Gigabit Network Connection' if=3Deth0 drv=3Digb > unused=3Digb_uio *Active* > 0000:05:00.1 'I350 Gigabit Network Connection' if=3Deth2 drv=3Digb > unused=3Digb_uio >=20 > Other network devices > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:03:00.0 'Device 15ad' unused=3Digb_uio > 0000:03:00.1 'Device 15ad' unused=3Digb_uio uml@uml:~/dpdk-2.2.0$ >=20 >=20 > Here is the dump --------> >=20 >=20 >=20 > ~/dpdk-2.2.0/examples/ip_pipeline/ip_pipeline/x86_64-native-linuxapp- > gcc/app$ sudo -E ./ip_pipeline -f /home/uml/dpdk- > 2.2.0/examples/ip_pipeline/config/l2fwd.cfg -p 0x01 [sudo] password for > uml: > [APP] Initializing CPU core map ... > [APP] CPU core mask =3D 0x0000000000000003 [APP] Initializing EAL ... > 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: Detected lcore 4 as core 4 on socket 0 > EAL: Detected lcore 5 as core 5 on socket 0 > EAL: Detected lcore 6 as core 6 on socket 0 > EAL: Detected lcore 7 as core 7 on socket 0 > EAL: Detected lcore 8 as core 0 on socket 0 > EAL: Detected lcore 9 as core 1 on socket 0 > EAL: Detected lcore 10 as core 2 on socket 0 > EAL: Detected lcore 11 as core 3 on socket 0 > EAL: Detected lcore 12 as core 4 on socket 0 > EAL: Detected lcore 13 as core 5 on socket 0 > EAL: Detected lcore 14 as core 6 on socket 0 > EAL: Detected lcore 15 as core 7 on socket 0 > EAL: Support maximum 128 logical core(s) by configuration. > EAL: Detected 16 lcore(s) > EAL: VFIO modules not all loaded, skip VFIO support... > EAL: Setting up physically contiguous memory... > EAL: Ask a virtual area of 0x40000000 bytes > EAL: Virtual area found at 0x7f24c0000000 (size =3D 0x40000000) > EAL: Requesting 1 pages of size 1024MB from socket 0 > EAL: TSC frequency is ~1999998 KHz > EAL: Master lcore 0 is ready (tid=3Dbc483940;cpuset=3D[0]) > EAL: lcore 1 is ready (tid=3Dbad86700;cpuset=3D[1]) > EAL: PCI device 0000:03:00.0 on NUMA socket 0 > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > EAL: Not managed by a supported kernel driver, skipped > EAL: PCI device 0000:03:00.1 on NUMA socket 0 > EAL: probe driver: 8086:15ad rte_ixgbe_pmd > EAL: Not managed by a supported kernel driver, skipped > EAL: PCI device 0000:04:00.0 on NUMA socket 0 > EAL: probe driver: 8086:10fb rte_ixgbe_pmd > EAL: PCI memory mapped at 0x7f2500000000 > EAL: PCI memory mapped at 0x7f2500080000 > PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5 > PMD: eth_ixgbe_dev_init(): port 0 vendorID=3D0x8086 deviceID=3D0x10fb > EAL: PCI device 0000:04:00.1 on NUMA socket 0 > EAL: probe driver: 8086:10fb rte_ixgbe_pmd > EAL: Not managed by a supported kernel driver, skipped > EAL: PCI device 0000:05:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1521 rte_igb_pmd > EAL: Not managed by a supported kernel driver, skipped > EAL: PCI device 0000:05:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1521 rte_igb_pmd > EAL: Not managed by a supported kernel driver, skipped > [APP] Initializing MEMPOOL0 ... > [APP] Initializing LINK0 (0) (1 RXQ, 1 TXQ) ... > PMD: ixgbe_dev_rx_queue_setup(): sw_ring=3D0x7f24fb128340 > sw_sc_ring=3D0x7f24fb127e00 hw_ring=3D0x7f24fb128880 > dma_addr=3D0xffb128880 > PMD: ixgbe_dev_tx_queue_setup(): sw_ring=3D0x7f24fb115c40 > hw_ring=3D0x7f24fb117c80 dma_addr=3D0xffb117c80 > PMD: ixgbe_set_tx_function(): Using simple tx code path > PMD: ixgbe_set_tx_function(): Vector tx enabled. > PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burs= t > size no less than 4 (port=3D0). > [APP] LINK0 (0) (10 Gbps) UP > [APP] Initializing MSGQ-REQ-PIPELINE0 ... > [APP] Initializing MSGQ-RSP-PIPELINE0 ... > [APP] Initializing MSGQ-REQ-CORE-s0c0 ... > [APP] Initializing MSGQ-RSP-CORE-s0c0 ... > [APP] Initializing MSGQ-REQ-PIPELINE1 ... > [APP] Initializing MSGQ-RSP-PIPELINE1 ... > [APP] Initializing MSGQ-REQ-CORE-s0c1 ... > [APP] Initializing MSGQ-RSP-CORE-s0c1 ... > [APP] Initializing PIPELINE0 ... > pipeline> [APP] Initializing PIPELINE1 ... > Cannot find LINK1 for RXQ1.0 Seems like you are having less ports than specified in l2fwd.cfg. In order = to run ip_pipeline with l2fwd.cfg configuration file, 4 ports are required.= So , you can either change configuration file and remove 3 extra ports (R= XQ1.0, RXQ2.0, RXQ3.0 and TXQ1.0, TXQ2.0, TXQ3.0) or bind 3 more ports to = dpdk and use the default l2fwd.cfg straightaway. Jasvinder