From: Amedeo Sapio <amedeo.sapio@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] MLX5 QP creation failure - cannot allocate memory
Date: Thu, 17 Jan 2019 00:07:46 +0300 [thread overview]
Message-ID: <CAMkTTJN7X=jPCFdf9Epy15DZ8e3YMJK4xtWbxWqwL+_YKYOnvQ@mail.gmail.com> (raw)
Hi all,
I am developing a DPDK program using a Mellanox ConnectX-5 100G.
My program starts N workers (one per core), and each worker deals with its
own dedicated TX and RX queue, therefore I need to setup N TX and N RX
queues.
For each RX queue I create a mbuf pool with:
n = 262144
cache size = 512
priv_size = 0
data_room_size = RTE_MBUF_DEFAULT_BUF_SIZE
For N<=4 everything works fine, but with N=8, 'rte_eth_dev_start' returns:
"Unknown error -12"
and the following error:
net_mlx5: port 0 Tx queue 0 QP creation failure
net_mlx5: port 0 Tx queue allocation failed: Cannot allocate memory
I tried
- to increment the number of Hugepages (up to 64x1G)
- change the pool size in different ways
- both dpdk 18.05 and 18.11
but with no success. Do you have any suggestions on what could be the issue?
Thanks for your help,
---
Amedeo
next reply other threads:[~2019-01-16 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 21:07 Amedeo Sapio [this message]
2019-01-17 1:45 ` Yongseok Koh
2019-01-17 8:52 ` Amedeo Sapio
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='CAMkTTJN7X=jPCFdf9Epy15DZ8e3YMJK4xtWbxWqwL+_YKYOnvQ@mail.gmail.com' \
--to=amedeo.sapio@gmail.com \
--cc=dev@dpdk.org \
/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).