From: "Zhang, Jerry" <jerry.zhang@intel.com>
To: jerry <jerry.lilijun@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "luonengjun@huawei.com" <luonengjun@huawei.com>
Subject: Re: [dpdk-dev] l2fwd mmap memory failed
Date: Sun, 14 Sep 2014 11:12:49 +0000 [thread overview]
Message-ID: <FA09AAB07F084C4DA208D537E2734D2C374B409E@CDSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <54155957.9000400@huawei.com>
Hi,
>-----Original Message-----
>From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of jerry
>Sent: Sunday, September 14, 2014 5:01 PM
>To: dev@dpdk.org
>Cc: luonengjun@huawei.com
>Subject: [dpdk-dev] l2fwd mmap memory failed
>
>Hi all,
>
>The l2fwd sample application starts failed in my environment with 90000 2M
>hugepages set up.
>It tells me that mmap failed: Cannot allocate memory.
>Is there a limited max hugepages or memory size for dpdk to mmap EAL
>memory?
>
>Some information as follows:
>
>1. Environment:
>Host OS: Suse11 Sp3 x86_64
>NIC: intel 82599
>DPDK: 1.6.0r2
>
>2. Hugepage Configuration in Kernel command line:
>hugepagesz=2M default_hugepagesz=2M hugepages=90000
>
>3. l2fwd command line:
>./build/l2fwd -c 0x3 -n 3 --socket-mem 2048 -- -q 1 -p 3
>
>4. cat /proc/meminfo:
>HugePages_Total: 90000
>HugePages_Free: 90000
>HugePages_Rsvd: 0
>HugePages_Surp: 0
>Hugepagesize: 2048 kB
>
>5. Error messages in dpdk log:
>Sun Sep 14 08:37:28 2014:EAL: Detected lcore 0 as core 0 on socket 0 Sun Sep 14
>08:37:28 2014:EAL: Detected lcore 1 as core 1 on socket 0 Sun Sep 14 08:37:28
>2014:EAL: Setting up memory...
>Sun Sep 14 08:38:44 2014:EAL: map_all_hugepages(): mmap failed: Cannot
>allocate memory Sun Sep 14 08:38:44 2014:EAL: Failed to mmap 2 MB
>hugepages Sun Sep 14 08:38:44 2014:EAL: Cannot init memory Sun Sep 14
>08:38:44 2014:EAL: Error - exiting with code: 1
> Cause: Sun Sep 14 08:38:44 2014:Invalid EAL parameters
>
>
>Anyone know the issue and the corresponding fix? Thanks.
It's a system mmap failure.
As you have to map so many huge pages, I suggest that you check /proc/sys/vm/max_map_count to see if the map count exceeds the max value.
next prev parent reply other threads:[~2014-09-14 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 9:01 jerry
2014-09-14 11:12 ` Zhang, Jerry [this message]
2014-09-15 0:59 ` jerry
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=FA09AAB07F084C4DA208D537E2734D2C374B409E@CDSMSX102.ccr.corp.intel.com \
--to=jerry.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jerry.lilijun@huawei.com \
--cc=luonengjun@huawei.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).