From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: "Alipour, Mehrdad" <malipour@ciena.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: rte_mempool_create fails with --no-huge
Date: Wed, 4 Dec 2024 23:51:21 +0300 [thread overview]
Message-ID: <20241204235121.2ad20665@sovereign> (raw)
In-Reply-To: <DM6PR04MB676159B502BB0C64A1BD0A25C4362@DM6PR04MB6761.namprd04.prod.outlook.com>
Hi Alipour,
It looks suspicious that on the host you don't see logs about loaded drivers,
like these ones that you see inside the VM:
> 2024-12-03 19:32:36.642042 EAL: open shared lib /usr/lib/dpdk/pmds-24.0/librte_net_fm10k.so.24.0
> 2024-12-03 19:32:36.642266 EAL: pmd.net.fm10k.init log level changed from disabled to notice
> 2024-12-03 19:32:36.642279 EAL: pmd.net.fm10k.driver log level changed from disabled to notice
> 2024-12-03 19:32:36.642285 EAL: open shared lib /usr/lib/dpdk/pmds-24.0/librte_net_qdma.so.24.0
> 2024-12-03 19:32:36.642581 EAL: open shared lib /usr/lib/dpdk/pmds-24.0/librte_net_vhost.so
> 2024-12-03 19:32:36.643201 EAL: lib.dmadev log level changed from disabled to info
> 2024-12-03 19:32:36.643264 EAL: Registered [vdpa] device class.
Can it be that DPDK on the host does not see shared libraries,
e.g. it is not installed in the system and LD_LIBRARY_PATH is not set
to shared library location?
Then mempool driver would just not be loaded to create a mempool.
next prev parent reply other threads:[~2024-12-04 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 19:54 Alipour, Mehrdad
2024-12-04 20:51 ` Dmitry Kozlyuk [this message]
2024-12-04 23:05 ` [**EXTERNAL**] " Alipour, Mehrdad
2024-12-05 8:30 ` David Marchand
2024-12-05 21:28 ` Alipour, Mehrdad
2024-12-06 7:38 ` 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=20241204235121.2ad20665@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=malipour@ciena.com \
/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).