From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Tao Peng <dev.pengtao@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] net_mlx5: priv allocation failure
Date: Fri, 18 May 2018 15:50:23 +0200 [thread overview]
Message-ID: <20180518135023.GN6497@6wind.com> (raw)
In-Reply-To: <CA+CVHvBWZ+sC1NAUTCySPC4bYhiG-UzADu6fvFxAHsrcfDGqsw@mail.gmail.com>
On Tue, Apr 24, 2018 at 10:24:54AM +0800, Tao Peng wrote:
> *And when I run testpmd , I get the same error:*
>
>
> $./testpmd -c 0xff00 -n 4 -- --rxq=2 --txq=2 -i
>
> EAL: Detected 64 lcore(s)
>
> EAL: No free hugepages reported in hugepages-1048576kB
>
> EAL: Probing VFIO support...
>
> EAL: WARNING: Master core has no memory on local socket!
>
> EAL: PCI device 0000:01:00.0 on NUMA socket 0
>
> EAL: probe driver: 15b3:1015 net_mlx5
>
> PMD: net_mlx5: PCI information matches, using device "mlx5_0" (SR-IOV:
> false, MPS: true)
>
> PMD: net_mlx5: 1 port(s) detected
>
> PMD: net_mlx5: priv allocation failure
>
> EAL: Requested device 0000:01:00.0 cannot be used
>
> EAL: PCI device 0000:01:00.1 on NUMA socket 0
>
> EAL: probe driver: 15b3:1015 net_mlx5
>
> PMD: net_mlx5: PCI information matches, using device "mlx5_1" (SR-IOV:
> false, MPS: true)
>
> PMD: net_mlx5: 1 port(s) detected
>
> PMD: net_mlx5: priv allocation failure
<snip>
> And, when I use 'sudo', the error will disappeared.
>
> $sudo ./testpmd -c 0xff00 -n 4 -- --rxq=2 --txq=2 -i
>
> EAL: Detected 64 lcore(s)
>
> EAL: No free hugepages reported in hugepages-1048576kB
>
> EAL: Probing VFIO support...
>
> EAL: PCI device 0000:01:00.0 on NUMA socket 0
>
> EAL: probe driver: 15b3:1015 net_mlx5
>
> PMD: net_mlx5: PCI information matches, using device "mlx5_0" (SR-IOV:
> false, MPS: true)
>
> PMD: net_mlx5: 1 port(s) detected
>
> PMD: net_mlx5: MPS is enabled
<snip>
You need to investigate "EAL: WARNING: Master core has no memory on local
socket!"
Hugepage memory files are possibly owned by root at this point. Those are
not cleaned up when DPDK applications exit. It's done on purpose to minimize
memory fragmentation over start/stop cycles.
Have a look at /dev/hugepage/rtemap_* files, e.g.:
# ls -l /dev/hugepages/
[...]
-rw------- 1 root root 2097152 May 14 10:13 rtemap_976
-rw------- 1 root root 2097152 May 14 10:13 rtemap_977
-rw------- 1 root root 2097152 May 14 10:13 rtemap_978
[...]
This means a mere user can't use them. In which case you need to chown/chmod
or remove them altogether.
Have you tried --no-huge?
--
Adrien Mazarguil
6WIND
prev parent reply other threads:[~2018-05-18 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 10:03 Tao Peng
2018-04-23 11:24 ` Adrien Mazarguil
2018-04-23 14:45 ` Tao Peng
2018-04-24 2:24 ` Tao Peng
2018-05-18 13:50 ` Adrien Mazarguil [this message]
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=20180518135023.GN6497@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev.pengtao@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).