Hi, The hash creation API throws the following error -- RING: Cannot reserve memory for tailq HASH: memory allocation failed
The timer subsystem init api throws this error -- EAL: memzone_reserve_aligned_thread_unsafe(): Number of requested memzone segments exceeds RTE_MAX_MEMZONE I did check the code and apparently the memzone and rte zmalloc related api's are not being able to allocate memory. Regards -Prashant On Thu, Mar 30, 2023 at 1:30 PM Bruce Richardson <bruce.richard...@intel.com> wrote: > > On Thu, Mar 30, 2023 at 10:30:24AM +0530, Prashant Upadhyaya wrote: > > Hi, > > > > While trying to port some code to VPP (which uses DPDK as the backend > > driver), I am running into a problem that calls to API's like > > rte_timer_subsystem_init, rte_hash_create are failing while allocation > > of memory. > > > > This is presumably because VPP inits the EAL with the following arguments -- > > > > -in-memory --no-telemetry --file-prefix vpp > > > > Is there is something that can be done eg. passing some more parms in > > the EAL initialization which hopefully wouldn't break VPP but will > > also be friendly to the RTE timer and hash functions too, that would > > be great, so requesting some advice here. > > > Hi, > > can you provide some more details on what the errors are that you are > receiving? Have you been able to dig a little deeper into what might be > causing the memory failures? The above flags alone are unlikely to cause > issues with hash or timer libraries, for example. > > /Bruce
