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 91ACC2C5D for ; Thu, 24 Mar 2016 16:23:34 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga101.jf.intel.com with ESMTP; 24 Mar 2016 08:22:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,385,1455004800"; d="scan'208,217";a="72553296" Received: from irsmsx105.ger.corp.intel.com ([163.33.3.28]) by fmsmga004.fm.intel.com with ESMTP; 24 Mar 2016 08:22:15 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.239]) by irsmsx105.ger.corp.intel.com ([169.254.7.35]) with mapi id 14.03.0248.002; Thu, 24 Mar 2016 15:22:13 +0000 From: "Singh, Jasvinder" To: Royce Niu CC: "users@dpdk.org" Thread-Topic: [dpdk-users] Why we need [MASTER] in DPDK Pipeline Thread-Index: AQHRhRvyEal5xzyg20GpC2sVDLDzi59nc5pggAC8WYCAAIMboA== Date: Thu, 24 Mar 2016 15:22:13 +0000 Message-ID: <54CBAA185211B4429112C315DA58FF6DDDAE91@IRSMSX103.ger.corp.intel.com> References: <54CBAA185211B4429112C315DA58FF6DDDA481@IRSMSX103.ger.corp.intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzRmY2JlMzItNzQ5My00YmQzLWE0ZTItYmIwMjI4NGQwNjE2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjZzN3U0ekgrdWQwY0pLY2dxdTRzeFVYa1E0QjhOeEJDYjJIRGJRTUJLUlU9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Why we need [MASTER] in DPDK Pipeline 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: Thu, 24 Mar 2016 15:23:35 -0000 Hi, From: Royce Niu [mailto:royceniu@gmail.com] Sent: Thursday, March 24, 2016 7:16 AM To: Singh, Jasvinder Cc: Royce Niu ; users@dpdk.org Subject: Re: [dpdk-users] Why we need [MASTER] in DPDK Pipeline Thanks! Your explanation is quite clear. But, we I assign one core to VM and use this one core to start the pipeline= . It shows : sudo ./build/ip_pipeline -f l2fwd.cfg -p 0x6 [APP] Initializing CPU core map ... PANIC in app_init_core_map(): Cannot create CPU core map 6: [./build/ip_pipeline() [0x431b43]] 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7efdd5090ec5= ]] 4: [./build/ip_pipeline(main+0x5f) [0x4306ff]] 3: [./build/ip_pipeline(app_init+0x14fb) [0x43f7ab]] 2: [./build/ip_pipeline(__rte_panic+0xc9) [0x42b11a]] 1: [./build/ip_pipeline(rte_dump_stack+0x1a) [0x4c9fba]] The config is : [PIPELINE0] type =3D MASTER core =3D 0 [PIPELINE1] type =3D PASS-THROUGH core =3D 0 pktq_in =3D RXQ0.0 RXQ1.0 pktq_out =3D TXQ1.0 TXQ0.0 The VM start cmd is : sudo taskset 0x10 ./qemu-system-x86_64 -enable-kvm -cpu host -m 1024M -smp = sockets=3D1,cores=3D1 -netdev tap,id=3Dhostnet0 -device virtio-net-pci,netd= ev=3Dhostnet0,id=3Dnet0,mac=3D52:54:00:5e:cc:f0 /trunk/template.img -charde= v socket,id=3Dchar0,path=3D/tmp/sn_vhost_vh0 -netdev type=3Dvhost-user,id= =3Dmynet0,chardev=3Dchar0,vhostforce -device virtio-net-pci,netdev=3Dmynet0= ,mac=3D52:54:00:02:d9:00 -chardev socket,id=3Dchar1,path=3D/tmp/sn_vhost_vh= 1 -netdev type=3Dvhost-user,id=3Dmynet1,chardev=3Dchar1,vhostforce -device = virtio-net-pci,netdev=3Dmynet1,mac=3D52:54:00:02:d9:01 -object memory-backe= nd-file,id=3Dmem,size=3D1024M,mem-path=3D/dev/hugepages,share=3Don -numa no= de,memdev=3Dmem -mem-prealloc -chardev pty,id=3Dcharserial0 -device isa-ser= ial,chardev=3Dcharserial0,id=3Dserial0 However, when I assign two vCPUs to the VM and assign P0 and P1 in differen= t vCPU. Everything is right. I tried running using single core on physical host and it worked. On VM, t= here shouldn't be any problem too. Perhaps something is missing in qemu sys= tem parameters settings. Jasvinder