From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: Cannot allocate mempool with --no-huge since DPDK 16.07 Date: Mon, 25 Sep 2017 10:13:35 +0200 Message-ID: <20170925081333.wlvtceflipekcdme@platinum> References: <371456982.11145391.1506007268500.JavaMail.zimbra@ulg.ac.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: tom.barbette@ulg.ac.be Return-path: Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id 4B5712C28 for ; Mon, 25 Sep 2017 10:13:43 +0200 (CEST) Content-Disposition: inline In-Reply-To: <371456982.11145391.1506007268500.JavaMail.zimbra@ulg.ac.be> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Tom, On Thu, Sep 21, 2017 at 05:21:08PM +0200, tom.barbette@ulg.ac.be wrote: > Hi all, > > I get a EINVAL since DPDK 16.07 when trying to allocate a mempool with rte_pktmbuf_pool_create. This is when I use --no-huge --vdev=eth_ring0. But this happens before accessing the virtual device in any ways. > > Which, btw shows the documentation is wrong as it indicates : > EINVAL - cache size provided is too large, or priv_size is not aligned. > Which is not the problem here (tried cache_size of 0, 64,256 and priv_size is 0). EINVAL can obviously come from elswhere. > > Any idea? Something changed in involved subsystems since 16.07? I first though your issue was related to this one: http://dpdk.org/ml/archives/dev/2017-June/067678.html But maybe it's just a memory issue. Can you try with less mbufs? testpmd --no-huge [...] -- --total-num-mbufs=4096 [...] If that fixes the issue, I'll check if we can change the return value to something clearer (ENOMEM?). Thanks, Olivier