DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jeff Wang <fatjeffw@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] testpmd app issues
Date: Tue, 17 Feb 2015 09:31:33 -0700	[thread overview]
Message-ID: <CAJKP2Zd49qC+kP9jpqVQ5AvWBwC0JuQCXFJkJ_os1-fjHW3Ymw@mail.gmail.com> (raw)

Hi,

I'm new to DPDK.

I have gone through the user guide, set up environment, hugepages. I can
get the helloworld app work. Now, when I tried to play with the testpmd
app, I got the following issue:

[root@localhost dpdk-1.8.0]# build/app/testpmd -c 0x2 -n1 -- -i
--nb-cores=1 --nb-ports=0x1

.....

EAL: TSC frequency is ~2594110 KHz
EAL: Master core 1 is ready (tid=e07b3840)
PMD: ENICPMD trace: rte_enic_pmd_init
EAL: PCI device 0000:02:00.0 on NUMA socket -1
EAL:   probe driver: 8086:10d3 rte_em_pmd
EAL:   0000:02:00.0 not managed by UIO driver, skipping
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   probe driver: 8086:10d3 rte_em_pmd
EAL:   PCI memory mapped at 0x7f06df800000
EAL:   PCI memory mapped at 0x7f06df820000
PMD: eth_em_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x10d3
EAL: PCI device 0000:04:00.0 on NUMA socket -1
EAL:   probe driver: 8086:10d3 rte_em_pmd
EAL:   0000:04:00.0 not managed by UIO driver, skipping
EAL: PCI device 0000:05:00.0 on NUMA socket -1
EAL:   probe driver: 8086:10d3 rte_em_pmd
EAL:   0000:05:00.0 not managed by UIO driver, skipping*PANIC in main():
Empty set of forwarding logical cores - check the core mask supplied
in the command parameters*
5: [build/app/testpmd() [0x428ea5]]
4: [/lib64/libc.so.6(__libc_start_main+0xf5) [0x7f06df8e2af5]]

.....

It says the core mask is not right. I set it to 0x2 because my CPU
only has 2 cores. I don't quite get it.

Can someone help me with this? And has anyone else encountered the same issue?

Thanks!

             reply	other threads:[~2015-02-17 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 16:31 Jeff Wang [this message]
2015-02-17 16:35 ` Bruce Richardson

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=CAJKP2Zd49qC+kP9jpqVQ5AvWBwC0JuQCXFJkJ_os1-fjHW3Ymw@mail.gmail.com \
    --to=fatjeffw@gmail.com \
    --cc=dev@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).