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

2024-12-05 Thread Alipour, Mehrdad
Hello David/Dmitry, After adding -d , I can now see all the pmd shared libs loading fine and rte_mempool_create works with --no-huge. Thanks a lot for your support! Regards, Mehrdad -Original Message- From: David Marchand Sent: December 5, 2024 3:30 AM To: Alipour, Mehrdad Cc

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

2024-12-04 Thread Alipour, Mehrdad
: December 4, 2024 3:51 PM To: Alipour, Mehrdad Cc: dev@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.642

rte_mempool_create fails with --no-huge

2024-12-03 Thread Alipour, Mehrdad
Hi, I am facing problem with rte_mempool_create when running my app with -no-huge after rte_eal_init succeeds. Note that this app works fine with hugepages but since it's purpose is unit testing certain packet processing logic, it has no requirements to have ports and the Linux may not necessar

[dpdk-dev] rte_table_hash_ext.c: rte_table_hash_ext_lookup is non-reentrant

2021-07-06 Thread Alipour, Mehrdad
Hi, We have tested lib/librte_table/rte_table_hash_ext.c: rte_table_hash_ext_lookup using dpdk 19.11 and it appears that the function is not reentrant safe causing incorrect hash lookup misses at very small rate (< 0.005%) when invoked by multiple threads in parallel. The reason for reentr

[dpdk-dev] RTE pipeline table lookup miss with > 1 core

2020-10-23 Thread Alipour, Mehrdad
Hi, I am testing a pipeline application with two or more cores using dpdk 19.05. The application consists of: Core1: forever get packets from an Ethernet IF (using rte_eth_rx_burst) Inspect packet header such as EtherType, UDP desp_port, etc; determine application (say ap