DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier MATZ <olivier.matz@6wind.com>
To: tom.barbette@ulg.ac.be
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Cannot allocate mempool with --no-huge since DPDK 16.07
Date: Mon, 25 Sep 2017 10:13:35 +0200	[thread overview]
Message-ID: <20170925081333.wlvtceflipekcdme@platinum> (raw)
In-Reply-To: <371456982.11145391.1506007268500.JavaMail.zimbra@ulg.ac.be>

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

      reply	other threads:[~2017-09-25  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 15:21 tom.barbette
2017-09-25  8:13 ` Olivier MATZ [this message]

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=20170925081333.wlvtceflipekcdme@platinum \
    --to=olivier.matz@6wind.com \
    --cc=dev@dpdk.org \
    --cc=tom.barbette@ulg.ac.be \
    /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).