DPDK usage discussions
 help / color / Atom feed
From: Vincent Li <vincent.mc.li@gmail.com>
To: Ding Ma <mdyuki1016@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>, users@dpdk.org
Subject: Re: [dpdk-users] Need help: Generate core list error. rte_eal port num [0] is not match the pciidlist [4]
Date: Wed, 3 Jun 2020 13:51:04 -0700 (PDT)
Message-ID: <alpine.OSX.2.21.2006031343530.43852@sea-ml-00029224.olympus.f5net.com> (raw)
In-Reply-To: <CA+h+_BtmD_GzAM1QGr9zcPrYGsqm79x0r0sB1A0XSfTtYrbJqA@mail.gmail.com>



On Tue, 2 Jun 2020, Ding Ma wrote:

> Really appreciate your help. Two follow-ups:
> - it actually works on 48 cores server and do you know why?  (The problem
> server is 96 cores)

I think Stephen might mean your pre-build DPDK might not be built with 32 
cores, I am not familiar with this neither, but I here is my grep search:

/usr/src/dpdk# egrep  'CORE|CPU' x86_64-native-linux-gcc/.config

CONFIG_RTE_MAX_LCORE=128
# Recognize/ignore architecture we compile for. AVX/AVX512 CPU flags for 
performance/power testing.
CONFIG_RTE_MAX_LCORE_FREQS=64
CONFIG_RTE_TEST_PMD_RECORD_CORE_CYCLES=n

I guess your pre-built DPDK might have CONFIG_RTE_MAX_LCORE built less 
than 96, you can either rebuilt your DPDK RPM package or rebuild from DPDK 
source with cores >= 96, say 128


> - which part in config I need to change? (Sorry I am a noob) . Also, I am
> using pre-built RPM to install dpdk, do I have to rebuild the RPM on 96
> cores server in order to run it on the 96 cores server?
> 
> On Tue, Jun 2, 2020 at 7:21 PM Stephen Hemminger <stephen@networkplumber.org>
> wrote:
> 
> > On Tue, 2 Jun 2020 18:04:57 -0700
> > Ding Ma <mdyuki1016@gmail.com> wrote:
> >
> > > Hope it's the right way to ask DPDK questions. I am new to DPDK world and
> > > got an error while setting up dpdk on my server. any idea about where I
> > > should look at?
> > >
> > >
> > >    1. Error: rte_eal port num [0] is not match the pciidlist [4]
> > >    2. EAL: Error - exiting with code: 1
> > >    3.   Cause: Generate core list error
> > >
> > >
> > > Full paste:
> > > ttps://pastebin.com/zea7514Y <https://pastebin.com/zea7514Y>
> >
> > Your DPDK is built for only 32 CPU's and you have a machine with 128.
> > Change your config and move on to the next issue.
> >
> > * There are patches in review to avoid this in future versions of DPDK.
> >
> 

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+h+_BuFT_cqGsxdyPOz8EtMOMdvZi4yWdW28=ZXsh70uL=Xzg@mail.gmail.com>
2020-06-03  1:04 ` Ding Ma
2020-06-03  2:21   ` Stephen Hemminger
2020-06-03  2:34     ` Ding Ma
2020-06-03 20:51       ` Vincent Li [this message]
2020-06-03 21:35         ` Ding Ma
2020-06-04  0:47           ` Vincent Li

Reply instructions:

You may reply publically 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=alpine.OSX.2.21.2006031343530.43852@sea-ml-00029224.olympus.f5net.com \
    --to=vincent.mc.li@gmail.com \
    --cc=mdyuki1016@gmail.com \
    --cc=stephen@networkplumber.org \
    --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

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox