[**EXTERNAL**] Re: rte_mempool_create fails with --no-huge

[Alipour, Mehrdad]

Hi Dmitry,

Your observation is good!
But I have the /usr/lib/dpdk/pmds-24.0 in the LD_LIBRARY_PATH but since the host does not have a match glibc, I have to run it with ld-linux-x86-64.so.2 specifying LD_LIBRARY_PATH with equivalent --library-path.

Here is the entire cmd I use to run testpmd:

sudo /lib/ld-linux-x86-64.so.2 --library-path /lib:/usr/lib:/usr/lib/dpdk:/usr/lib/dpdk/pmds-24.0:/ciena/lib /usr/bin/dpdk-testpmd -c 000F -n 2 --log-level=eal,8 --no-huge -m 4095 --no-pci -- -i --nb-cores=2 --total-num-mbufs=2048

Despite the /lib/dpdk/pmds-24.0 libs being visible, the rte_eal_init does not load any of these shared libs while it does when I run it inside the VM.
Would appreciate if you can think of any reasons rte_eal_init does not trigger loading those shared libs in the host run instance.

Regards,
Mehrdad

-----Original Message-----
From: Dmitry Kozlyuk <dmitry.kozliuk at gmail.com> 
Sent: December 4, 2024 3:51 PM
To: Alipour, Mehrdad <malipour at ciena.com>
Cc: dev at dpdk.org
Subject: [**EXTERNAL**] Re: rte_mempool_create fails with --no-huge

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.