On Tue, 7 Nov 2023 08:22:37 +0100
Morten Brørup <m...@smartsharesystems.com> wrote:
> > > Or are you saying that if they want to use dumpcap, they must choose
> > a thread safe pool type for their application (regardless if the
> > application is single-threaded or not)?
> >
> > There is no command line of EAL nature in dumpcap.
> > This is intentional.
> > QED: overriding default pool type is not going to be a possible
>
> The preferred mbuf pool type can configured in the primary process by EAL
> params. If so configured, it is stored in a memzone named
> "mbuf_user_pool_ops".
> And if it is set there, the secondary process will also use it as its
> preferred mbuf pool type.
I notice that no other app or example is using the create_by_ops except
pdump/pcapng/dumpcap.
~/DPDK/main/examples $ git grep rte_pktmbuf_pool_create_by_ops
~/DPDK/main/app $ git grep rte_pktmbuf_pool_create_by_ops
dumpcap/main.c: mp = rte_pktmbuf_pool_create_by_ops(pool_name, num_mbufs,
pdump/main.c: mbuf_pool =
rte_pktmbuf_pool_create_by_ops(mempool_name,
test/test_pcapng.c: mp = rte_pktmbuf_pool_create_by_ops("pcapng_test_pool",
IOV_MAX + NUM_PACKETS,
