From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by dpdk.org (Postfix) with ESMTP id C7AE22E81 for ; Mon, 15 Sep 2014 02:55:33 +0200 (CEST) Received: from 172.24.2.119 (EHLO szxeml409-hub.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BZL21964; Mon, 15 Sep 2014 09:00:54 +0800 (CST) Received: from [127.0.0.1] (10.177.19.236) by szxeml409-hub.china.huawei.com (10.82.67.136) with Microsoft SMTP Server id 14.3.158.1; Mon, 15 Sep 2014 09:00:48 +0800 Message-ID: <54163A0E.8060603@huawei.com> Date: Mon, 15 Sep 2014 08:59:58 +0800 From: jerry User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: "Zhang, Jerry" , "dev@dpdk.org" References: <54155957.9000400@huawei.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.19.236] X-CFilter-Loop: Reflected Cc: "luonengjun@huawei.com" Subject: Re: [dpdk-dev] l2fwd mmap memory failed X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 00:55:35 -0000 Hi, On 2014/9/14 19:12, Zhang, Jerry wrote: > 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. > > That works when echo 200000 > /proc/sys/vm/max_map_count. I have tried the count 100000 and it still failed. This reason may be that dpdk calls map_all_hugepages() twice in my opinion. Thanks for your help.