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 try to confirm that this is the problem by adding log messages to announce when rte_eal_init(), rte_ring_create(), and rte_mempool_create() are about to be called and check the order that those messages appear in your logs. Or you could run VPP in a debugger and set breakpoints on those 3 functions and check what order the breakpoints are hit. If the calls to rte_ring_create() and rte_mempool_create() come before rte_eal_init() has been called, you need to adjust your plugin code so it calls them after rte_eal_init() has been called. If not, and rte_eal_init() is being called first, then I have no further guesses on the source of your issues. -Matt On Tue, Feb 7, 2023 at 7:23 PM kk <aihujiang1...@gmail.com> wrote: > 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. > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22576): https://lists.fd.io/g/vpp-dev/message/22576 Mute This Topic: https://lists.fd.io/mt/96804295/21656 Mute #acl_plugin:https://lists.fd.io/g/vpp-dev/mutehashtag/acl_plugin Mute #dpdk:https://lists.fd.io/g/vpp-dev/mutehashtag/dpdk Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
