From: Kai Zhang <kay21s@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Issue with more Cores assigned: Cannot mmap device resource file
Date: Sat, 11 Mar 2017 23:45:24 +0800 [thread overview]
Message-ID: <CACKSPmcib_8BuUDfFy2_5ibAkoQ+ogKi-C=hvvjebZ4cv5OBqQ@mail.gmail.com> (raw)
In-Reply-To: <B6D80026-C2CF-4D76-B695-E37D14BC1D7A@intel.com>
Hi Keith,
Thank you for your reply.
I have tested my program on two machines
A) 1 x Intel E5-2650 v4, 12 cores [UMA]
B) 2 x Intel E5-2640 v4, 10 cores [NUMA]
I am very sure that the primary process uses different cores with the
secondary process. The strange thing is that my program works correctly on
machine *B*. But on machine *A*, the above issue happens with more than 4
cores assigned to the secondary process.
I have tried to assign cores 1-5 to the secondary process and also
tried other core assignment policies, but the error still happens
rte_eal_init() with more than 4 cores.
Regards,
Kai
On Sat, Mar 11, 2017 at 10:52 PM, Wiles, Keith <keith.wiles@intel.com>
wrote:
>
> > On Mar 10, 2017, at 9:35 PM, Kai Zhang <kay21s@gmail.com> wrote:
> >
> > Hi, there
> >
> > I am using DPDK-16.11 on XL710 40GbE NIC. OS: CentOS 7.3.1611 with Linux
> > kernel version 3.8.0-30.
> >
> > I have a master process and a secondary process. When I run the secondary
> > process with less than or equal to 4 cores, it works correctly. Such as:
> > sudo ./program -l 4,5,6,7 -n 4 --proc-type=secondary
> > sudo ./program -c 0x0f -n 4 --proc-type=secondary
> >
> > However, there will be error in the rte_eal_init if I assign more than 4
> > cores.
> > sudo ./program -l 0,1,2,3,4 -n 4 --proc-type=secondary
> > sudo ./program -c 0x1f -n 4 --proc-type=secondary
> >
> > EAL: Cannot mmap device resource file
> > /sys/bus/pci/devices/0000:02:00.0/resource0 to address: 0x7fff65bfc000
> > EAL: Error - exiting with code: 1
> > Cause: Requested device 0000:02:00.0 cannot be used
>
> I assume you have at least 8 cores. Have you tried -l 1-5 on the secondary
> process.
>
> You did not show the primary process command line, but the if you use 1-5
> then you can only give primary process -l 6-7 or two cores. It is always a
> reasonable thing is to leave core zero for linux to use.
>
> Also it could be you ran out of memory or hugepages you allocated to the
> system.
>
> >
> > Anyone knows why this happens?
> >
> > Thanks a lot,
> > Kai Zhang
>
> Regards,
> Keith
>
>
next prev parent reply other threads:[~2017-03-11 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 3:35 Kai Zhang
2017-03-11 14:52 ` Wiles, Keith
2017-03-11 15:45 ` Kai Zhang [this message]
2017-03-11 18:59 ` Wiles, Keith
2017-03-12 3:21 ` Kai Zhang
2017-03-12 3:29 ` Kai Zhang
2017-03-12 10:32 ` Wiles, Keith
2017-03-12 10:39 ` Kai Zhang
2017-03-12 18:55 ` Wiles, Keith
2017-03-12 19:24 ` Wiles, Keith
2017-03-12 23:44 ` Kai Zhang
2017-03-13 9:58 ` Van Haaren, Harry
2017-03-13 10:59 ` Kai Zhang
2017-03-15 14:56 David Coen
2017-03-15 15:48 David Coen
2017-03-15 17:02 ` Kai Zhang
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='CACKSPmcib_8BuUDfFy2_5ibAkoQ+ogKi-C=hvvjebZ4cv5OBqQ@mail.gmail.com' \
--to=kay21s@gmail.com \
--cc=keith.wiles@intel.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).