From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id 64D485934 for ; Thu, 10 Nov 2016 14:34:29 +0100 (CET) Received: from lfbn-1-5996-232.w90-110.abo.wanadoo.fr ([90.110.195.232] helo=[192.168.1.13]) by mail.droids-corp.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1c4pYC-0000Op-6A; Thu, 10 Nov 2016 14:37:56 +0100 To: "Wiles, Keith" , Keren Hochman References: <6BBBABF1-45E1-4260-BE26-9C556C47B825@intel.com> Cc: Christian Ehrhardt , dev From: Olivier Matz Message-ID: <0fa3b042-bb5f-04f9-5ac4-bb70c8765340@6wind.com> Date: Thu, 10 Nov 2016 14:34:23 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0 MIME-Version: 1.0 In-Reply-To: <6BBBABF1-45E1-4260-BE26-9C556C47B825@intel.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] disable hugepages 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: Thu, 10 Nov 2016 13:34:29 -0000 On 11/10/2016 02:10 PM, Wiles, Keith wrote: > >> On Nov 10, 2016, at 6:32 AM, Keren Hochman wrote: >> >> I tried using the following dpdk options: >> --no-huge --vdev eth_pcap0 ,rx_pcap=/t1,tx_pcap=/t2 >> *It's worked but the number of elements is limited, although the machine >> has enough free memory. *rte_mempool_create is failed when I'm trying to >> allocate more memory. Is there any limitation on the memory beside the >> machine? > > DPDK will just use the standard linux memory allocator, so no limitation in DPDK. Now you could be hitting the limit as a user, need to check your system to make sure you can allocate that much memory to a user. Try using the command ulimit and see what it reports. > > I do not remember exactly how to change limits except with ulimit command. I may have modified /etc/security/limits.conf file. I don't think it's a ulimit issue. Actually, the memory is reserved once at startup. The -m EAL option allows to specify the amount of memory allocated: -m MB Memory to allocate (see also --socket-mem) So I guess setting it to an higher value (256?) would do the job. Regards, Olivier