On Wed, 26 Mar 2025 10:27:40 +0000 "Kompella V, Purnima" <kompella.purn...@commscope.com> wrote:
> Hi Stephen > > Isn't it possible to gather all the MEMPOOL_REGISTER_OPS (xxx) calls to a > separate .c file in the dpdk source code > Like say drivers/mempool/common/rte_mempool_ops_reg.c containing below lines > > MEMPOOL_REGISTER_OPS(ops_stack); > MEMPOOL_REGISTER_OPS(ops_lf_stack); > MEMPOOL_REGISTER_OPS(ops_bucket); > MEMPOOL_REGISTER_OPS(ops_bucket); > MEMPOOL_REGISTER_OPS(octeontx_fpavf_ops); That would be inflexible. Not every build needs all the ops. If you want to fix, a better approach would be to harden the registration process. Initializers and destructors are a problematic construct to debug.