From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: Royce Niu <royceniu@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Why we need [MASTER] in DPDK Pipeline
Date: Thu, 24 Mar 2016 15:22:13 +0000 [thread overview]
Message-ID: <54CBAA185211B4429112C315DA58FF6DDDAE91@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAOwUCNtyTbKRvKqby8GHFTYPOsWWDpDJy4Yz-F49+XE87qXTYA@mail.gmail.com>
Hi,
From: Royce Niu [mailto:royceniu@gmail.com]
Sent: Thursday, March 24, 2016 7:16 AM
To: Singh, Jasvinder <jasvinder.singh@intel.com>
Cc: Royce Niu <royceniu@gmail.com>; 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 = MASTER
core = 0
[PIPELINE1]
type = PASS-THROUGH
core = 0
pktq_in = RXQ0.0 RXQ1.0
pktq_out = TXQ1.0 TXQ0.0
The VM start cmd is :
sudo taskset 0x10 ./qemu-system-x86_64 -enable-kvm -cpu host -m 1024M -smp sockets=1,cores=1 -netdev tap,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5e:cc:f0 /trunk/template.img -chardev socket,id=char0,path=/tmp/sn_vhost_vh0 -netdev type=vhost-user,id=mynet0,chardev=char0,vhostforce -device virtio-net-pci,netdev=mynet0,mac=52:54:00:02:d9:00 -chardev socket,id=char1,path=/tmp/sn_vhost_vh1 -netdev type=vhost-user,id=mynet1,chardev=char1,vhostforce -device virtio-net-pci,netdev=mynet1,mac=52:54:00:02:d9:01 -object memory-backend-file,id=mem,size=1024M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0
However, when I assign two vCPUs to the VM and assign P0 and P1 in different vCPU. Everything is right.
I tried running using single core on physical host and it worked. On VM, there shouldn't be any problem too. Perhaps something is missing in qemu system parameters settings.
Jasvinder
prev parent reply other threads:[~2016-03-24 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 15:51 Royce Niu
2016-03-23 20:06 ` Singh, Jasvinder
2016-03-24 7:16 ` Royce Niu
2016-03-24 15:22 ` Singh, Jasvinder [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54CBAA185211B4429112C315DA58FF6DDDAE91@IRSMSX103.ger.corp.intel.com \
--to=jasvinder.singh@intel.com \
--cc=royceniu@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).