You haven't shared any details of where you placed these calls in the dpdk
plugin, but I suspect that they were successful because they were executed
after the dpdk plugin had already called rte_eal_init(). When called from
your plugin, rte_eal_init() had probably not been called yet.
You could tr
I read the official example given by dpdk. The two function interfaces
"rte_ring_create and rte_mempool_create" should indeed be called after
rte_eal_init(). The problem is that I have no problem calling these two
function interfaces in the vpp dpdk plug-in, which is very strange.
-=-=-=-=-=-=-
Are you calling those functions in an init/config function for your plugin?
Maybe they are being called before the dpdk plugin has executed
rte_eal_init().
-Matt
On Tue, Feb 7, 2023 at 4:05 AM kk wrote:
> Hello everyone, I wrote a vpp plug-in by myself. I called the dpdk
> function interface "
Hello everyone, I wrote a vpp plug-in by myself. I called the dpdk function
interface "rte_ring_create and rte_mempool_create" in this plug-in, and then it
will prompt:
"MEMPOOL: Cannot allocate tailq entry!
Problem getting send ring
RING: Cannot reserve memory for tailq
RING: Cannot reserve memo
