DPDK usage discussions
 help / color / mirror / Atom feed
From: Ding Ma <mdyuki1016@gmail.com>
To: Vincent Li <vincent.mc.li@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 14:35:36 -0700	[thread overview]
Message-ID: <CA+h+_BuUO4uskn3+z9P-8MjkCUfaXuLi_H9LLk9MdaE_imFwqA@mail.gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.21.2006031343530.43852@sea-ml-00029224.olympus.f5net.com>

Thanks for reply.
BTW I guess "CONFIG_RTE_MAX_LCORE=128" means no more than 128 cores.  But
what does "CONFIG_RTE_MAX_LCORE_FREQS=64" mean?

On Wed, Jun 3, 2020 at 1:51 PM Vincent Li <vincent.mc.li@gmail.com> wrote:

>
>
> 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	other threads:[~2020-06-03 21:35 UTC|newest]

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
2020-06-03 21:35         ` Ding Ma [this message]
2020-06-04  0:47           ` Vincent Li

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=CA+h+_BuUO4uskn3+z9P-8MjkCUfaXuLi_H9LLk9MdaE_imFwqA@mail.gmail.com \
    --to=mdyuki1016@gmail.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    --cc=vincent.mc.li@gmail.com \
    /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).