From mboxrd@z Thu Jan 1 00:00:00 1970 From: jerry Subject: l2fwd mmap memory failed Date: Sun, 14 Sep 2014 17:01:11 +0800 Message-ID: <54155957.9000400@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: luonengjun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org To: Return-path: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 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. B.R. Jerry