From: Prashanth Fernando <prashanth.fernando@tatacommunications.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] How to address the error “MBUF: error setting mempool handler” seen with DPDK 20.11
Date: Mon, 7 Jun 2021 15:37:04 +0000 [thread overview]
Message-ID: <PU1PR04MB23120B2801EBAA5FB9C444AAF8389@PU1PR04MB2312.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <PU1PR04MB2312E1DD894CC726003D4065F83E9@PU1PR04MB2312.apcprd04.prod.outlook.com>
Update:
Had few issues with DPDK 20.11 in Centos-7.
* Installing Mellanox libverbs somehow affects the cflags and ldflags for dpdk libdpdk.pc
* pkg-config from the installed target was also incorrect.
Manually updating libdpdk.pc to include the static libraries under -Wl,--whole-archive and -Wl,--no-whole-archive
Regards,
Prashanth
From: Prashanth Fernando
Sent: 02 June 2021 02:12
To: users@dpdk.org
Subject: How to address the error “MBUF: error setting mempool handler” seen with DPDK 20.11
Hi all,
I did a static linking of libdpdk to my application and when I start the application EAL init fails.
Logs:
EAL: Detected 80 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: No legacy callbacks, legacy socket not created
MBUF: error setting mempool handler
EAL: Error - exiting with code: 1
Cause: Cannot init packet mbuf pool Invalid argument
I installed DPDK-20.11 in my test server, using the following commands.
# meson build
#cd build
#ninja ; ninja install
I built my application Makefile taking l2fwd Makefile as an example, not sure what I am missing.
Looking out for suggestions.
Regards,
Prashanth
Tata Communications - Public
Tata Communications - Public
next prev parent reply other threads:[~2021-06-07 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 20:42 Prashanth Fernando
2021-06-07 15:37 ` Prashanth Fernando [this message]
2021-06-07 16:35 ` 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=PU1PR04MB23120B2801EBAA5FB9C444AAF8389@PU1PR04MB2312.apcprd04.prod.outlook.com \
--to=prashanth.fernando@tatacommunications.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).