From: Pinak Tripathy <Pinak.Tripathy@exfo.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Problem in dpdk mpool initialization in dpdk20.11
Date: Mon, 8 Mar 2021 07:45:53 +0000 [thread overview]
Message-ID: <BYAPR11MB27108071AC5CABC9B8DF36C6E9939@BYAPR11MB2710.namprd11.prod.outlook.com> (raw)
Hi,
I am porting the application from dpdk 17.11 to dpdk 20.11
Application uses centos7.9 and melanox 5.2.2 PMD
Below api call works fine in dpdk17.11 but fails in dpdk20.11
rte_pktmbuf_pool_create ("mbuf_pool_0", (4096 * 64 * 16 - 1), 512, 0, RTE_MBUF_DEFAULT_BUF_SIZE) fails with error no 22 (EINVAL)
-MBUF: error setting mempool handler
-PANIC in app_init_mbuf_pools():
-Cannot create mbuf pool on socket 0 (errno=22)
On adding debug trace found that rte_mempool_ops_table.num_ops =0.
Not sure what is causing this issue. Can you please point out likely cause of this?
Best Regards,
Pinak
next reply other threads:[~2021-03-08 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 7:45 Pinak Tripathy [this message]
2021-03-08 8:42 ` Pinak Tripathy
2021-03-08 10:16 ` David Marchand
2021-03-08 11:18 ` [dpdk-users] [E!] : " Pinak Tripathy
2021-03-08 12:47 ` [dpdk-users] " David Marchand
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=BYAPR11MB27108071AC5CABC9B8DF36C6E9939@BYAPR11MB2710.namprd11.prod.outlook.com \
--to=pinak.tripathy@exfo.com \
--cc=users@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).