From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: Royce Niu <royceniu@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Request an example config for DPDK IP PIPELINE
Date: Thu, 28 Jan 2016 14:14:55 +0000 [thread overview]
Message-ID: <54CBAA185211B4429112C315DA58FF6DDB5149@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <56AA0736.3080908@intel.com>
Hi Royce,
>
> On 25/01/2016 17:21, Royce Niu wrote:
> > $ sudo build/ip_pipeline -f config/l3fwd.cfg -p 0x3 [APP] Initializing
> > CPU core map ...
> > PANIC in app_init_core_mask():
> > Cannot create CPU core mask
> > 6: [build/ip_pipeline() [0x431b43]]
> > 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
> > [0x7f6417199ec5]]
> > 4: [build/ip_pipeline(main+0x5f) [0x4306ff]]
> > 3: [build/ip_pipeline(app_init+0x1bff) [0x43feaf]]
> > 2: [build/ip_pipeline(__rte_panic+0xc9) [0x42b11a]]
> > 1: [build/ip_pipeline(rte_dump_stack+0x1a) [0x4c9fca]]
> >
> > Cfg:
> >
> > [PIPELINE0]
> > type = MASTER
> > core = 0
> >
> > [PIPELINE1]
> > type = PASS-THROUGH
> > core = 1
> > pktq_in = RXQ0.0 RXQ1.0
> > pktq_out = TXQ1.0 TXQ0.0
> >
In the above configuration, you are using two cores. In case, if you are running IP_Pipeline application in VM, you have to bind right number of cores. To do so, you need to set -smp parameter used in qemu as below-
–smp sockets=1,cores=2 (in case pipeline app requires more cores to be used, then assign more cores).
Hope, it will fix the above error.
Thanks,
Jasvinder
next prev parent reply other threads:[~2016-01-28 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:40 Royce Niu
2016-01-25 15:42 ` Thomas Monjalon
2016-01-25 15:46 ` Royce Niu
2016-01-25 15:58 ` Thomas Monjalon
2016-01-25 16:03 ` Royce Niu
2016-01-25 17:00 ` Singh, Jasvinder
2016-01-25 17:09 ` Royce Niu
2016-01-25 17:18 ` Singh, Jasvinder
2016-01-25 17:21 ` Royce Niu
[not found] ` <56AA0736.3080908@intel.com>
2016-01-28 14:14 ` Singh, Jasvinder [this message]
2016-01-28 14:26 ` Royce Niu
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=54CBAA185211B4429112C315DA58FF6DDB5149@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).