[dpdk-dev] dpdk-testpmd app with SRIOV VF on Kubernetes POD not working

2021-07-15 Thread Truring Team
Hi Everyone,


We have Kubernetes setup where Master Node and one worker node are there
and tried running dpdk-testpmd on POD



So Master Node and Worker Node are AWS VM which has ixgbevf VF interfaces
and binded one interface with dpdk igb_uio then expose the interface inside
POD with multus cni and SR-IOV Network Device Plugin used and exposed
interface showing inside POD



Also created the Hugepages on worker node before joining cluster and then
POD yaml file used hugepages-2Mi:100Mi with help of Kubernetes
documentation
https://kubernetes.io/docs/tasks/manage-hugepages/scheduling-hugepages/

  Hugepages are showing in node and inside POD as well


NIC Detail:
*00:04.0 Ethernet controller [0200]: Intel Corporation 82599 Ethernet
Controller Virtual Function [8086:10ed] (rev 01)*

*dpdk-testpmd giving  segmentation fault on PODs*



After build dpdk-20.11 inside POD run the dpdk-testpmd then following
segment fault occurs



[root@centos7-testpmd dpdk-20.11]#* gdb ./build/app/dpdk-testpmd*

GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7

Copyright (C) 2013 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later 

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.  Type "show copying"

and "show warranty" for details.

This GDB was configured as "x86_64-redhat-linux-gnu".

For bug reporting instructions, please see:

...

Reading symbols from /home/sandeep/dpdk-20.11/build/app/dpdk-testpmd...(no
debugging symbols found)...done.

(gdb) r -l 0-3 -n 4 -- -i

Starting program: /home/sandeep/dpdk-20.11/./build/app/dpdk-testpmd -l 0-3
-n 4 -- -i

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib64/libthread_db.so.1".

EAL: Detected 4 lcore(s)

EAL: Detected 1 NUMA nodes

[New Thread 0x76a71700 (LWP 29508)]

EAL: Multi-process socket /var/run/dpdk/rte/mp_socket

[New Thread 0x76270700 (LWP 29509)]

EAL: Selected IOVA mode 'PA'

EAL: No available hugepages reported in hugepages-1048576kB

EAL: Probing VFIO support...

[New Thread 0x75a6f700 (LWP 29510)]

[New Thread 0x7526e700 (LWP 29511)]

[New Thread 0x74a6d700 (LWP 29512)]

EAL:   Invalid NUMA socket, default to 0

EAL:   Invalid NUMA socket, default to 0

EAL: Probe PCI driver: net_ixgbe_vf (8086:10ed) device: :00:04.0
(socket 0)

[New Thread 0x7426c700 (LWP 29513)]

EAL: No legacy callbacks, legacy socket not created

Interactive-mode selected

testpmd: create a new mbuf pool : n=171456, size=2176, socket=0

testpmd: preferred mempool ops selected: ring_mp_mc



Program received signal SIGBUS, Bus error.

0x009ffa36 in alloc_seg ()

Missing separate debuginfos, use: debuginfo-install
glibc-2.17-324.el7_9.x86_64 libgcc-4.8.5-44.el7.x86_64
libpcap-1.5.3-12.el7.x86_64 numactl-libs-2.0.12-5.el7.x86_64
zlib-1.2.7-19.el7_9.x86_64

(gdb) *bt*

*#0  0x009ffa36 in alloc_seg ()*

#1  0x00a0043b in alloc_seg_walk ()

#2  0x009e35ab in rte_memseg_list_walk_thread_unsafe ()

#3  0x00a00d32 in eal_memalloc_alloc_seg_bulk ()

#4  0x009f0374 in alloc_pages_on_heap ()

#5  0x009f065b in try_expand_heap ()

#6  0x009f0a91 in alloc_more_mem_on_socket ()

#7  0x009f115e in malloc_heap_alloc ()

#8  0x009e3ed1 in rte_memzone_reserve_thread_safe ()

#9  0x009d671e in rte_mempool_populate_default ()

#10 0x009c93af in rte_pktmbuf_pool_create_by_ops ()

#11 0x009c9478 in rte_pktmbuf_pool_create ()

#12 0x0072b233 in mbuf_pool_create ()

#13 0x004266d4 in main ()

(gdb)




Can anyone help in resolving this issue ?


Best Regard

Puneet


Re: [dpdk-dev] dpdk-testpmd app with SRIOV VF on Kubernetes POD not working

2021-07-20 Thread Truring Team
Hi Everyone ,

Can someone please look into this  and analyse logs ?
I need help to proceed further .

Best Regards
Puneet

On Fri, 16 Jul 2021 at 09:34, Truring Team  wrote:

> Hi Everyone,
>
>
> We have Kubernetes setup where Master Node and one worker node are there
> and tried running dpdk-testpmd on POD
>
>
>
> So Master Node and Worker Node are AWS VM which has ixgbevf VF interfaces
> and binded one interface with dpdk igb_uio then expose the interface inside
> POD with multus cni and SR-IOV Network Device Plugin used and exposed
> interface showing inside POD
>
>
>
> Also created the Hugepages on worker node before joining cluster and then
> POD yaml file used hugepages-2Mi:100Mi with help of Kubernetes
> documentation
> https://kubernetes.io/docs/tasks/manage-hugepages/scheduling-hugepages/
>
>   Hugepages are showing in node and inside POD as well
>
>
> NIC Detail:
> *00:04.0 Ethernet controller [0200]: Intel Corporation 82599 Ethernet
> Controller Virtual Function [8086:10ed] (rev 01)*
>
> *dpdk-testpmd giving  segmentation fault on PODs*
>
>
>
> After build dpdk-20.11 inside POD run the dpdk-testpmd then following
> segment fault occurs
>
>
>
> [root@centos7-testpmd dpdk-20.11]#* gdb ./build/app/dpdk-testpmd*
>
> GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7
>
> Copyright (C) 2013 Free Software Foundation, Inc.
>
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
>
> This is free software: you are free to change and redistribute it.
>
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>
> and "show warranty" for details.
>
> This GDB was configured as "x86_64-redhat-linux-gnu".
>
> For bug reporting instructions, please see:
>
> <http://www.gnu.org/software/gdb/bugs/>...
>
> Reading symbols from /home/sandeep/dpdk-20.11/build/app/dpdk-testpmd...(no
> debugging symbols found)...done.
>
> (gdb) r -l 0-3 -n 4 -- -i
>
> Starting program: /home/sandeep/dpdk-20.11/./build/app/dpdk-testpmd -l 0-3
> -n 4 -- -i
>
> [Thread debugging using libthread_db enabled]
>
> Using host libthread_db library "/lib64/libthread_db.so.1".
>
> EAL: Detected 4 lcore(s)
>
> EAL: Detected 1 NUMA nodes
>
> [New Thread 0x76a71700 (LWP 29508)]
>
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
>
> [New Thread 0x76270700 (LWP 29509)]
>
> EAL: Selected IOVA mode 'PA'
>
> EAL: No available hugepages reported in hugepages-1048576kB
>
> EAL: Probing VFIO support...
>
> [New Thread 0x75a6f700 (LWP 29510)]
>
> [New Thread 0x7526e700 (LWP 29511)]
>
> [New Thread 0x74a6d700 (LWP 29512)]
>
> EAL:   Invalid NUMA socket, default to 0
>
> EAL:   Invalid NUMA socket, default to 0
>
> EAL: Probe PCI driver: net_ixgbe_vf (8086:10ed) device: :00:04.0
> (socket 0)
>
> [New Thread 0x7426c700 (LWP 29513)]
>
> EAL: No legacy callbacks, legacy socket not created
>
> Interactive-mode selected
>
> testpmd: create a new mbuf pool : n=171456, size=2176, socket=0
>
> testpmd: preferred mempool ops selected: ring_mp_mc
>
>
>
> Program received signal SIGBUS, Bus error.
>
> 0x009ffa36 in alloc_seg ()
>
> Missing separate debuginfos, use: debuginfo-install
> glibc-2.17-324.el7_9.x86_64 libgcc-4.8.5-44.el7.x86_64
> libpcap-1.5.3-12.el7.x86_64 numactl-libs-2.0.12-5.el7.x86_64
> zlib-1.2.7-19.el7_9.x86_64
>
> (gdb) *bt*
>
> *#0  0x009ffa36 in alloc_seg ()*
>
> #1  0x00a0043b in alloc_seg_walk ()
>
> #2  0x009e35ab in rte_memseg_list_walk_thread_unsafe ()
>
> #3  0x00a00d32 in eal_memalloc_alloc_seg_bulk ()
>
> #4  0x009f0374 in alloc_pages_on_heap ()
>
> #5  0x009f065b in try_expand_heap ()
>
> #6  0x009f0a91 in alloc_more_mem_on_socket ()
>
> #7  0x009f115e in malloc_heap_alloc ()
>
> #8  0x009e3ed1 in rte_memzone_reserve_thread_safe ()
>
> #9  0x009d671e in rte_mempool_populate_default ()
>
> #10 0x009c93af in rte_pktmbuf_pool_create_by_ops ()
>
> #11 0x009c9478 in rte_pktmbuf_pool_create ()
>
> #12 0x0072b233 in mbuf_pool_create ()
>
> #13 0x004266d4 in main ()
>
> (gdb)
>
>
>
>
> Can anyone help in resolving this issue ?
>
>
> Best Regard
>
> Puneet
>


[dpdk-dev] How to Enable Mellanox Driver Compilation with DPDK20.11

2021-01-28 Thread Truring Team
Hi Team ,

Can someone help me to figure out how to  enable the Mellanox Driver flag
in meson.build file , so that dpdk 20.11 compiles with mlx driver enabled.

Best Regards
Puneet


Re: [dpdk-dev] How to Enable Mellanox Driver Compilation with DPDK20.11

2021-01-29 Thread Truring Team
Hi Bruce ,
Thanks a lot for your help.
After installing below packages mlx is compiled .

yum -y groupinstall "Infiniband Support"

yum install -y gcc kernel-devel-`uname -r` numactl-devel.x86_64
librdmacm-devel libmnl-devel


*find . -name *.a | grep mlx*

*./drivers/libtmp_rte_common_mlx5.a*

*./drivers/librte_common_mlx5.a*

*./drivers/libtmp_rte_net_mlx4.a*

*./drivers/librte_net_mlx4.a*

*./drivers/libtmp_rte_regex_mlx5.a*

*./drivers/librte_regex_mlx5.a*

*./drivers/libtmp_rte_vdpa_mlx5.a*

*./drivers/librte_vdpa_mlx5.a*

*./drivers/libtmp_rte_net_mlx5.a*

*./drivers/librte_net_mlx5.a*


Best Regards
Puneet

On Fri, 29 Jan 2021 at 15:38, Bruce Richardson 
wrote:

> On Fri, Jan 29, 2021 at 11:50:08AM +0530, Truring Team wrote:
> > Hi Team ,
> >
> > Can someone help me to figure out how to  enable the Mellanox Driver flag
> > in meson.build file , so that dpdk 20.11 compiles with mlx driver
> enabled.
> >
> If the driver is not being built there should be a reason given in the
> build configuration summary when you run meson. This is almost certainly
> that you are missing a library dependency for it, since all drivers are
> enabled unless their dependencies are missing.
>
> /Bruce
>


[dpdk-dev] DPDK issue with Marvell NIC QLogic Corp. FastLinQ QL41000

2021-05-25 Thread Truring Team
Hi Team,

I am trying to run the dpdk test-pmd application (DPDK 20.11 and DPDK
21.05) with NIC QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE
Controller but facing following issues:

If someone can look into the following logs and help me figure out the
issue?



1. DPDK 20.11 ( Using 1 GB hugepages)

   gdb ./dpdk-testpmd

12:45:59.347 §GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7

12:45:59.347 §Copyright (C) 2013 Free Software Foundation, Inc.

12:45:59.348 §License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html

12:45:59.349 §This is free software: you are free to change and
redistribute it.

12:45:59.349 §There is NO WARRANTY, to the extent permitted by law.  Type
"show copying"

12:45:59.349 §and "show warranty" for details.

12:45:59.350 §This GDB was configured as "x86_64-redhat-linux-gnu".

12:45:59.351 §For bug reporting instructions, please see:

12:45:59.351 §http://www.gnu.org/software/gdb/bugs/...

12:45:59.415 §Reading symbols from
/home/itwsadmin/dpdk-20.11/build/app/dpdk-testpmd...(no debugging symbols
found)...done.

12:46:11.492 §(gdb) r -l 0-5 -n4 -- -i

12:46:11.493 §Starting program:
/home/itwsadmin/dpdk-20.11/build/app/./dpdk-testpmd -l 0-5 -n4 -- -i

12:46:11.717 §[Thread debugging using libthread_db enabled]

12:46:11.719 §Using host libthread_db library "/lib64/libthread_db.so.1".

12:46:11.768 §EAL: Detected 6 lcore(s)

12:46:11.769 §EAL: Detected 1 NUMA nodes

12:46:11.769 §[New Thread 0x76a71700 (LWP 23184)]

12:46:11.769 §EAL: Multi-process socket /var/run/dpdk/rte/mp_socket

12:46:11.770 §[New Thread 0x76270700 (LWP 23185)]

12:46:11.792 §EAL: Selected IOVA mode 'PA'

12:46:11.792 §EAL: No free hugepages reported in hugepages-2048kB

12:46:11.792 §EAL: No available hugepages reported in hugepages-2048kB

12:46:11.854 §EAL: Probing VFIO support...

12:46:11.855 §[New Thread 0x75a6f700 (LWP 23186)]

12:46:11.855 §[New Thread 0x7526e700 (LWP 23187)]

12:46:11.855 §[New Thread 0x74a6d700 (LWP 23188)]

12:46:11.855 §[New Thread 0x7426c700 (LWP 23189)]

12:46:11.856 §[New Thread 0x73a6b700 (LWP 23190)]

12:46:11.896 §EAL: Probe PCI driver: net_qede (1077:8070) device:
:65:00.0 (socket 0)

12:46:11.915 §

12:46:11.915 §Program received signal SIGSEGV, Segmentation fault.

12:46:11.916 §0x00ec5b20 in ecore_fw_overlay_mem_alloc ()

12:46:11.916 §Missing separate debuginfos, use: debuginfo-install
glibc-2.17-324.el7_9.x86_64 libgcc-4.8.5-44.el7.x86_64
libpcap-1.5.3-12.el7.x86_64 numactl-libs-2.0.12-5.el7.x86_64
zlib-1.2.7-19.el7_9.x86_64

12:46:14.542 §(gdb) bt

12:46:14.548 §#0  0x00ec5b20 in ecore_fw_overlay_mem_alloc ()

12:46:14.548 §#1  0x00eb811e in ecore_hw_init ()

12:46:14.549 §#2  0x00ef7397 in qed_slowpath_start ()

12:46:14.549 §#3  0x00ef0483 in qede_common_dev_init ()

12:46:14.549 §#4  0x00ef1113 in qede_eth_dev_pci_probe ()

12:46:14.549 §#5  0x00a4450b in pci_probe ()

12:46:14.550 §#6  0x009dbc6c in rte_bus_probe ()

12:46:14.550 §#7  0x009fa91c in rte_eal_init ()

12:46:14.617 §#8  0x00425db1 in main ()

12:46:17.052 §(gdb) quit

12:46:17.056 §A debugging session is active.

12:46:17.056 §

12:46:17.057 §Inferior 1 [process 23180] will be killed.





2. *DPDK 21.05:*

   ./dpdk-testpmd -l 0-5 -n4 -- -i

12:46:46.257 §EAL: Detected 6 lcore(s)

12:46:46.257 §EAL: Detected 1 NUMA nodes

12:46:46.258 §EAL: Detected static linkage of DPDK

12:46:46.260 §EAL: Multi-process socket /var/run/dpdk/rte/mp_socket

12:46:46.285 §EAL: Selected IOVA mode 'PA'

12:46:46.285 §EAL: No free 2048 kB hugepages reported on node 0

12:46:46.288 §EAL: No available 2048 kB hugepages reported

12:46:46.382 §EAL: Probe PCI driver: net_qede (1077:8070) device:
:65:00.0 (socket 0)

12:46:46.403 §[QEDE PMD: ()]ecore_load_mcp_offsets:The address of the MCP
scratch-pad is not configured

12:46:46.403 §[QEDE PMD: ()]ecore_mcp_cmd_init:MCP is not initialized

12:46:46.404 §[QEDE PMD: ()]ecore_mcp_cmd_and_union:MFW is not initialized!

12:46:46.404 §[QEDE PMD: ()]ecore_hw_get_nvm_info:Shared memory not
initialized

12:46:46.404 §[QEDE PMD: ()]ecore_hw_prepare_single:Failed to get HW
information

12:46:46.404 §[qed_probe:74(65:00.0:dpdk-port-0)]hw prepare failed

12:46:46.404 §[qede_common_dev_init:2566(65:00.0:dpdk-port-0)]qede probe
failed rc -3

12:46:46.406 §EAL: Requested device :65:00.0 cannot be used

12:46:46.408 §TELEMETRY: No legacy callbacks, legacy socket not created

12:46:46.423 §testpmd: No probed ethernet devices

12:46:46.461 §Interactive-mode selected

12:46:46.519 §testpmd: create a new mbuf pool : n=187456,
size=2176, socket=0

12:46:46.522 §testpmd: preferred mempool ops selected: ring_mp_mc

12:46:46.540 §Done





System Information:

*ethtool -i p2p1*
driver: qede
version: 8.33.0.20
*firmware-version: mfw 8.24.44.0 storm 8.33.11.0*
expansion-rom-version:
bus-info: :65:00.0
supports-statistics: yes
supports-test: ye

Re: [dpdk-dev] [dpdk-users] DPDK issue with Marvell NIC QLogic Corp. FastLinQ QL41000

2021-05-25 Thread Truring Team
Hi Nishant,

cat /proc/meminfo
11:59:29.200 §MemTotal:   23101672 kB
11:59:29.200 §MemFree:15254764 kB
11:59:29.200 §MemAvailable:   19243184 kB
11:59:29.200 §Buffers:6792 kB
11:59:29.201 §Cached:  4084844 kB
11:59:29.201 §SwapCached:0 kB
11:59:29.201 §Active:  3609016 kB
11:59:29.201 §Inactive:1175160 kB
11:59:29.201 §Active(anon): 695644 kB
11:59:29.202 §Inactive(anon):19716 kB
11:59:29.202 §Active(file):2913372 kB
11:59:29.202 §Inactive(file):  1155444 kB
11:59:29.202 §Unevictable:   0 kB
11:59:29.202 §Mlocked:   0 kB
11:59:29.203 §SwapTotal:  11665404 kB
11:59:29.204 §SwapFree:   11665404 kB
11:59:29.204 §Dirty:32 kB
11:59:29.204 §Writeback: 0 kB
11:59:29.204 §AnonPages:694764 kB
11:59:29.205 §Mapped:   140220 kB
11:59:29.205 §Shmem: 22800 kB
11:59:29.205 §Slab: 445016 kB
11:59:29.205 §SReclaimable: 289968 kB
11:59:29.205 §SUnreclaim:   155048 kB
11:59:29.206 §KernelStack:   16624 kB
11:59:29.206 §PageTables:35892 kB
11:59:29.206 §NFS_Unstable:  0 kB
11:59:29.206 §Bounce:0 kB
11:59:29.206 §WritebackTmp:  0 kB
11:59:29.207 §CommitLimit:22167664 kB
11:59:29.207 §Committed_AS:4342668 kB
11:59:29.207 §VmallocTotal:   34359738367 kB
11:59:29.207 §VmallocUsed:  463188 kB
11:59:29.207 §VmallocChunk:   34358835196 kB
11:59:29.208 §HardwareCorrupted: 0 kB
11:59:29.208 §AnonHugePages:329728 kB
11:59:29.208 §CmaTotal:  0 kB
11:59:29.209 §CmaFree:   0 kB
11:59:29.209 §HugePages_Total:1024
11:59:29.209 §HugePages_Free: 1019
11:59:29.209 §HugePages_Rsvd:0
11:59:29.209 §HugePages_Surp:0
11:59:29.209 §Hugepagesize:   2048 kB
11:59:29.209 §DirectMap4k:  381760 kB
11:59:29.209 §DirectMap2M:13973504 kB
11:59:29.215 §DirectMap1G:11534336 kB

Regards


On Wed, 26 May 2021 at 09:43, Nishant Verma  wrote:

> Can you paste output of /proc/meminfo ?
>
>
>
> Regards,
> NV
>
> On Tue, May 25, 2021 at 9:52 PM Truring Team  wrote:
>
>> Hi Team,
>>
>> I am trying to run the dpdk test-pmd application (DPDK 20.11 and DPDK
>> 21.05) with NIC QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE
>> Controller but facing following issues:
>>
>> If someone can look into the following logs and help me figure out the
>> issue?
>>
>>
>>
>> 1. DPDK 20.11 ( Using 1 GB hugepages)
>>
>>gdb ./dpdk-testpmd
>>
>> 12:45:59.347 §GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7
>>
>> 12:45:59.347 §Copyright (C) 2013 Free Software Foundation, Inc.
>>
>> 12:45:59.348 §License GPLv3+: GNU GPL version 3 or later
>> http://gnu.org/licenses/gpl.html
>>
>> 12:45:59.349 §This is free software: you are free to change and
>> redistribute it.
>>
>> 12:45:59.349 §There is NO WARRANTY, to the extent permitted by law.  Type
>> "show copying"
>>
>> 12:45:59.349 §and "show warranty" for details.
>>
>> 12:45:59.350 §This GDB was configured as "x86_64-redhat-linux-gnu".
>>
>> 12:45:59.351 §For bug reporting instructions, please see:
>>
>> 12:45:59.351 §http://www.gnu.org/software/gdb/bugs/...
>>
>> 12:45:59.415 §Reading symbols from
>> /home/itwsadmin/dpdk-20.11/build/app/dpdk-testpmd...(no debugging symbols
>> found)...done.
>>
>> 12:46:11.492 §(gdb) r -l 0-5 -n4 -- -i
>>
>> 12:46:11.493 §Starting program:
>> /home/itwsadmin/dpdk-20.11/build/app/./dpdk-testpmd -l 0-5 -n4 -- -i
>>
>> 12:46:11.717 §[Thread debugging using libthread_db enabled]
>>
>> 12:46:11.719 §Using host libthread_db library "/lib64/libthread_db.so.1".
>>
>> 12:46:11.768 §EAL: Detected 6 lcore(s)
>>
>> 12:46:11.769 §EAL: Detected 1 NUMA nodes
>>
>> 12:46:11.769 §[New Thread 0x76a71700 (LWP 23184)]
>>
>> 12:46:11.769 §EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
>>
>> 12:46:11.770 §[New Thread 0x76270700 (LWP 23185)]
>>
>> 12:46:11.792 §EAL: Selected IOVA mode 'PA'
>>
>> 12:46:11.792 §EAL: No free hugepages reported in hugepages-2048kB
>>
>> 12:46:11.792 §EAL: No available hugepages reported in hugepages-2048kB
>>
>> 12:46:11.854 §EAL: Probing VFIO support...
>>
>> 12:46:11.855 §[New Thread 0x75a6f700 (LWP 23186)]
>>
>> 12:46:11.855 §[New Thread 0x7526e700 (LWP 23187)]
>>
>> 12:46:11.855 §[New Thread 0x74a6d700 (LWP 23188)]
>>
>> 12:46:11.855 §[New Thread 0x7426c700 (LWP 23189)]
>>
>> 12:46:11.856 §[New Thread 0x73a6b700 (LWP 2319

Re: [dpdk-dev] [dpdk-users] DPDK issue with Marvell NIC QLogic Corp. FastLinQ QL41000

2021-05-25 Thread Truring Team
Yes , I have configured it via grub.

Grub:
"default_hugepagesz=1G hugepagesz=1G hugepages=2"
grub2-mkconfig -o /boot/grub2/grub.cfg

Manual:
mkdir /dev/hugepages1G
mount -t hugetlbfs -o pagesize=1G none /dev/hugepages1G
echo 2 >
/sys/devices/system/node/node1/hugepages/hugepages-1048576kB/nr_hugepages

Regards
Puneet

On Wed, 26 May 2021 at 10:05, Nishant Verma  wrote:

> meminfo states: Hugepagesize:1048576 kB
> But  in your initial mail you state Hugepage size is 1G.
>
> have you configured HugePage via grub ?
>
>
> Thanks.
>
> Regards,
> NV
>
> On Wed, May 26, 2021 at 12:21 AM Truring Team  wrote:
>
>> Hi Nishant,
>>
>> cat /proc/meminfo
>> 11:59:29.200 §MemTotal:   23101672 kB
>> 11:59:29.200 §MemFree:15254764 kB
>> 11:59:29.200 §MemAvailable:   19243184 kB
>> 11:59:29.200 §Buffers:6792 kB
>> 11:59:29.201 §Cached:  4084844 kB
>> 11:59:29.201 §SwapCached:0 kB
>> 11:59:29.201 §Active:  3609016 kB
>> 11:59:29.201 §Inactive:1175160 kB
>> 11:59:29.201 §Active(anon): 695644 kB
>> 11:59:29.202 §Inactive(anon):19716 kB
>> 11:59:29.202 §Active(file):2913372 kB
>> 11:59:29.202 §Inactive(file):  1155444 kB
>> 11:59:29.202 §Unevictable:   0 kB
>> 11:59:29.202 §Mlocked:   0 kB
>> 11:59:29.203 §SwapTotal:  11665404 kB
>> 11:59:29.204 §SwapFree:   11665404 kB
>> 11:59:29.204 §Dirty:32 kB
>> 11:59:29.204 §Writeback: 0 kB
>> 11:59:29.204 §AnonPages:694764 kB
>> 11:59:29.205 §Mapped:   140220 kB
>> 11:59:29.205 §Shmem: 22800 kB
>> 11:59:29.205 §Slab: 445016 kB
>> 11:59:29.205 §SReclaimable: 289968 kB
>> 11:59:29.205 §SUnreclaim:   155048 kB
>> 11:59:29.206 §KernelStack:   16624 kB
>> 11:59:29.206 §PageTables:35892 kB
>> 11:59:29.206 §NFS_Unstable:  0 kB
>> 11:59:29.206 §Bounce:0 kB
>> 11:59:29.206 §WritebackTmp:  0 kB
>> 11:59:29.207 §CommitLimit:22167664 kB
>> 11:59:29.207 §Committed_AS:4342668 kB
>> 11:59:29.207 §VmallocTotal:   34359738367 kB
>> 11:59:29.207 §VmallocUsed:  463188 kB
>> 11:59:29.207 §VmallocChunk:   34358835196 kB
>> 11:59:29.208 §HardwareCorrupted: 0 kB
>> 11:59:29.208 §AnonHugePages:329728 kB
>> 11:59:29.208 §CmaTotal:  0 kB
>> 11:59:29.209 §CmaFree:   0 kB
>> 11:59:29.209 §HugePages_Total:1024
>> 11:59:29.209 §HugePages_Free: 1019
>> 11:59:29.209 §HugePages_Rsvd:0
>> 11:59:29.209 §HugePages_Surp:0
>> 11:59:29.209 §Hugepagesize:   2048 kB
>> 11:59:29.209 §DirectMap4k:  381760 kB
>> 11:59:29.209 §DirectMap2M:13973504 kB
>> 11:59:29.215 §DirectMap1G:11534336 kB
>>
>> Regards
>>
>>
>> On Wed, 26 May 2021 at 09:43, Nishant Verma  wrote:
>>
>>> Can you paste output of /proc/meminfo ?
>>>
>>>
>>>
>>> Regards,
>>> NV
>>>
>>> On Tue, May 25, 2021 at 9:52 PM Truring Team 
>>> wrote:
>>>
>>>> Hi Team,
>>>>
>>>> I am trying to run the dpdk test-pmd application (DPDK 20.11 and DPDK
>>>> 21.05) with NIC QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE
>>>> Controller but facing following issues:
>>>>
>>>> If someone can look into the following logs and help me figure out the
>>>> issue?
>>>>
>>>>
>>>>
>>>> 1. DPDK 20.11 ( Using 1 GB hugepages)
>>>>
>>>>gdb ./dpdk-testpmd
>>>>
>>>> 12:45:59.347 §GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7
>>>>
>>>> 12:45:59.347 §Copyright (C) 2013 Free Software Foundation, Inc.
>>>>
>>>> 12:45:59.348 §License GPLv3+: GNU GPL version 3 or later
>>>> http://gnu.org/licenses/gpl.html
>>>>
>>>> 12:45:59.349 §This is free software: you are free to change and
>>>> redistribute it.
>>>>
>>>> 12:45:59.349 §There is NO WARRANTY, to the extent permitted by law.
>>>> Type
>>>> "show copying"
>>>>
>>>> 12:45:59.349 §and "show warranty" for details.
>>>>
>>>> 12:45:59.350 §This GDB was configured as "x86_64-redhat-linux-gnu".
>>>>
>>>> 12:45:59.351 §For bug reporting instructions, please see:
>>>>
>>>> 12:45:59.351 §http://www.gnu.org/software/gdb/bugs/

[dpdk-dev] DPDK 20.11 Static vs Dynamic Linking- l2fwd issue

2021-01-19 Thread Truring Team
Hi Team,

I am facing one issue with dpdk 20.11 Release, compiled the l2fwd app with
make static , its throwing following error while running the app:

Problematic Use Case:
cd dpdk-20.11/examples/l2fwd
export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
*make static *
./build/l2fwd -l 0-3 -n 4 -- -q 1 -p 1
EAL: Detected 6 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: No legacy callbacks, legacy socket not created
MAC updating enabled

*EAL: Error - exiting with code: 1  Cause: No Ethernet ports - bye*

Working use Case:
But when I am compiling l2fwd with *make* , then it's *working fine*.
cd dpdk-20.11/examples/l2fwd
export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
*make*
export LD_LIBRARY_PATH=/home/upfuser/dpdk-20.11/build//lib:$LD_LIBRARY_PATH
./build/l2fwd -l 0-3 -n 4 -- -q 1 -p 1
MAC updating enabled
Notice: odd number of ports in portmask.
Lcore 0: RX port 0 TX port 0
Initializing port 0... done:
Port 0, MAC address: DE:AD:CE:EF:85:81
Checking link status.done
Port 0 Link up at 1 Gbps FDX Autoneg
L2FWD: lcore 1 has nothing to do
L2FWD: lcore 2 has nothing to do
L2FWD: lcore 3 has nothing to do
L2FWD: entering main loop on lcore 0
L2FWD:  -- lcoreid=0 portid=0

Can someone help me to figure out the root cause why this happening.

Thanks


Re: [dpdk-dev] DPDK 20.11 Static vs Dynamic Linking- l2fwd issue

2021-01-19 Thread Truring Team
cat /etc/redhat-release
CentOS Linux release 7.8.2003 (Core)


pkg-config --version
0.27.1


pkg-config --static --libs libdpdk
Package libdpdk was not found in the pkg-config search path.
Perhaps you should add the directory containing `libdpdk.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libdpdk' found

locate libdpdk.pc
/home/user/dpdk-20.11/build/meson-private/libdpdk.pc
/usr/local/lib64/pkgconfig/libdpdk.pc


Thanks

On Tue, 19 Jan 2021 at 16:12, Bruce Richardson 
wrote:

> On Tue, Jan 19, 2021 at 10:40:10AM +, Bruce Richardson wrote:
> > On Tue, Jan 19, 2021 at 03:36:18PM +0530, Truring Team wrote:
> > > Hi Team,
> > >
> > > I am facing one issue with dpdk 20.11 Release, compiled the l2fwd app
> with
> > > make static , its throwing following error while running the app:
> > >
> > > Problematic Use Case:
> > > cd dpdk-20.11/examples/l2fwd
> > > export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
> > > *make static *
> > > ./build/l2fwd -l 0-3 -n 4 -- -q 1 -p 1
> > > EAL: Detected 6 lcore(s)
> > > EAL: Detected 1 NUMA nodes
> > > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> > > EAL: Selected IOVA mode 'PA'
> > > EAL: No available hugepages reported in hugepages-1048576kB
> > > EAL: Probing VFIO support...
> > > EAL: No legacy callbacks, legacy socket not created
> > > MAC updating enabled
> > >
> > > *EAL: Error - exiting with code: 1  Cause: No Ethernet ports - bye*
> > >
> > 
> > > Can someone help me to figure out the root cause why this happening.
> > >
> >
> > It seems like the static libs for the drivers are not linked in for the
> > "make static" case. Can you please check the following:
> >
> > * What OS/distro are you using, and what is the pkg-config version? The
> >   version of pkg-config included in RHEL/Centos is known to have some
> >   issues in linking DPDK.
> Missed clarification - RHEL/Centos *7* only. RHEL 8 is fine.
>
> > * What is the output when you run "pkg-config --static --libs libdpdk"
>


Re: [dpdk-dev] DPDK 20.11 Static vs Dynamic Linking- l2fwd issue

2021-01-19 Thread Truring Team
export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig


pkg-config --static --libs libdpdk
-Wl,--whole-archive -Wl,--no-whole-archive -Wl,--as-needed -pthread
-L/usr/local/lib64 -l:librte_common_cpt.a -l:librte_common_dpaax.a
-l:librte_common_iavf.a -l:librte_common_octeontx.a
-l:librte_common_octeontx2.a -l:librte_common_sfc_efx.a
-l:librte_bus_dpaa.a -l:librte_bus_fslmc.a -l:librte_bus_ifpga.a
-l:librte_bus_pci.a -l:librte_bus_vdev.a -l:librte_bus_vmbus.a
-l:librte_common_qat.a -l:librte_mempool_bucket.a -l:librte_mempool_dpaa.a
-l:librte_mempool_dpaa2.a -l:librte_mempool_octeontx.a
-l:librte_mempool_octeontx2.a -l:librte_mempool_ring.a
-l:librte_mempool_stack.a -l:librte_net_af_packet.a -l:librte_net_ark.a
-l:librte_net_atlantic.a -l:librte_net_avp.a -l:librte_net_axgbe.a
-l:librte_net_bond.a -l:librte_net_bnx2x.a -l:librte_net_bnxt.a
-l:librte_net_cxgbe.a -l:librte_net_dpaa.a -l:librte_net_dpaa2.a
-l:librte_net_e1000.a -l:librte_net_ena.a -l:librte_net_enetc.a
-l:librte_net_enic.a -l:librte_net_failsafe.a -l:librte_net_fm10k.a
-l:librte_net_i40e.a -l:librte_net_hinic.a -l:librte_net_hns3.a
-l:librte_net_iavf.a -l:librte_net_ice.a -l:librte_net_igc.a
-l:librte_net_ixgbe.a -l:librte_net_kni.a -l:librte_net_liquidio.a
-l:librte_net_memif.a -l:librte_net_netvsc.a -l:librte_net_nfp.a
-l:librte_net_null.a -l:librte_net_octeontx.a -l:librte_net_octeontx2.a
-l:librte_net_pcap.a -l:librte_net_pfe.a -l:librte_net_qede.a
-l:librte_net_ring.a -l:librte_net_sfc.a -l:librte_net_softnic.a
-l:librte_net_tap.a -l:librte_net_thunderx.a -l:librte_net_txgbe.a
-l:librte_net_vdev_netvsc.a -l:librte_net_vhost.a -l:librte_net_virtio.a
-l:librte_net_vmxnet3.a -l:librte_raw_dpaa2_cmdif.a
-l:librte_raw_dpaa2_qdma.a -l:librte_raw_ioat.a -l:librte_raw_ntb.a
-l:librte_raw_octeontx2_dma.a -l:librte_raw_octeontx2_ep.a
-l:librte_raw_skeleton.a -l:librte_crypto_bcmfs.a
-l:librte_crypto_caam_jr.a -l:librte_crypto_ccp.a
-l:librte_crypto_dpaa_sec.a -l:librte_crypto_dpaa2_sec.a
-l:librte_crypto_nitrox.a -l:librte_crypto_null.a
-l:librte_crypto_octeontx.a -l:librte_crypto_octeontx2.a
-l:librte_crypto_openssl.a -l:librte_crypto_scheduler.a
-l:librte_crypto_virtio.a -l:librte_compress_octeontx.a
-l:librte_compress_zlib.a -l:librte_regex_octeontx2.a -l:librte_vdpa_ifc.a
-l:librte_event_dlb.a -l:librte_event_dlb2.a -l:librte_event_dpaa.a
-l:librte_event_dpaa2.a -l:librte_event_octeontx2.a -l:librte_event_opdl.a
-l:librte_event_skeleton.a -l:librte_event_sw.a -l:librte_event_dsw.a
-l:librte_event_octeontx.a -l:librte_baseband_null.a
-l:librte_baseband_turbo_sw.a -l:librte_baseband_fpga_lte_fec.a
-l:librte_baseband_fpga_5gnr_fec.a -l:librte_baseband_acc100.a
-l:librte_node.a -l:librte_graph.a -l:librte_bpf.a
-l:librte_flow_classify.a -l:librte_pipeline.a -l:librte_table.a
-l:librte_port.a -l:librte_fib.a -l:librte_ipsec.a -l:librte_vhost.a
-l:librte_stack.a -l:librte_security.a -l:librte_sched.a
-l:librte_reorder.a -l:librte_rib.a -l:librte_regexdev.a -l:librte_rawdev.a
-l:librte_pdump.a -l:librte_power.a -l:librte_member.a -l:librte_lpm.a
-l:librte_latencystats.a -l:librte_kni.a -l:librte_jobstats.a
-l:librte_ip_frag.a -l:librte_gso.a -l:librte_gro.a -l:librte_eventdev.a
-l:librte_efd.a -l:librte_distributor.a -l:librte_cryptodev.a
-l:librte_compressdev.a -l:librte_cfgfile.a -l:librte_bitratestats.a
-l:librte_bbdev.a -l:librte_acl.a -l:librte_timer.a -l:librte_hash.a
-l:librte_metrics.a -l:librte_cmdline.a -l:librte_pci.a -l:librte_ethdev.a
-l:librte_meter.a -l:librte_net.a -l:librte_mbuf.a -l:librte_mempool.a
-l:librte_rcu.a -l:librte_ring.a -l:librte_eal.a -l:librte_telemetry.a
-l:librte_kvargs.a -lcrypto -lz -ljansson -lrte_node -lrte_graph -lrte_bpf
-lrte_flow_classify -lrte_pipeline -lrte_table -lrte_port -lrte_fib
-lrte_ipsec -lrte_vhost -lrte_stack -lrte_security -lrte_sched
-lrte_reorder -lrte_rib -lrte_regexdev -lrte_rawdev -lrte_pdump -lrte_power
-lrte_member -lrte_lpm -lrte_latencystats -lrte_kni -lrte_jobstats
-lrte_ip_frag -lrte_gso -lrte_gro -lrte_eventdev -lrte_efd
-lrte_distributor -lrte_cryptodev -lrte_compressdev -lrte_cfgfile
-lrte_bitratestats -lrte_bbdev -lrte_acl -lrte_timer -lrte_hash
-lrte_metrics -lrte_cmdline -lrte_pci -lrte_ethdev -lrte_meter -lrte_net
-lrte_mbuf -lrte_mempool -lrte_rcu -lrte_ring -lrte_eal -lrte_telemetry
-lrte_kvargs -lm -ldl -lnuma -lpcap

On Tue, 19 Jan 2021 at 16:51, Truring Team  wrote:

> cat /etc/redhat-release
> CentOS Linux release 7.8.2003 (Core)
>
>
> pkg-config --version
> 0.27.1
>
>
> pkg-config --static --libs libdpdk
> Package libdpdk was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libdpdk.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'libdpdk' found
>
> locate libdpdk.pc
> /home/user/dpdk-20.11/build/meson-private/libdpdk.pc
> /usr/local/lib64/pkgconfig/libdpdk.pc
>
>
> Thanks
>
> On Tue, 19 Jan 2021 at 16:12, Bruce Richardson 
> wrote:
>