RE: tailqs issue

["Kompella V, Purnima" <Kompella.Purnima@commscope.com>]

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);
Etc
Etc
This way both Primary and Secondary processes can get the same order of OPs irrespective of the order of dpdk libs listing in their compilation.
In the current method, each lib calls MEMPOOL_REGISTER_OPS(xx) in its own source code and hence the order of OPs in struct rte_mempool_ops::name[] in a DPDK process depends on the order of libs listed during compilation.

Also, in struct rte_mempool, if we can add ops_name as a new data-member (along with ops_index that's already present), then 
	Primary process can populate struct rte_mempool::ops_name with the name of the OP corresponding to struct rte_mempool::ops_index it had used to create this mempool. 
	Secondary processes can validate whether in the secondary processes' OPs database, struct rte_mempool::ops_index is matching the struct rte_mempool::ops_name 

If a mismatch is detected, Secondary can call panic -- this kind of early failure is better than everything only 'looking good` but not actually being good.

Regards,
Purnima



-----Original Message-----
From: Lombardo, Ed <Ed.Lombardo@netscout.com> 
Sent: Wednesday, March 26, 2025 4:27 AM
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Kompella V, Purnima <Kompella.Purnima@commscope.com>; users@dpdk.org
Subject: RE: tailqs issue

CAUTION: This message originated from an External Source outside of CommScope.com. This may be a phishing email that can result in unauthorized access to CommScope. Please use caution when opening attachments, clicking links, scanning QR codes, or responding. You can report suspicious emails directly in Microsoft Outlook.




Hi Stephen,
Is there development work to remove this restriction, or is this impossible?

Thanks,
Ed

-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Tuesday, March 25, 2025 6:42 PM
To: Lombardo, Ed <Ed.Lombardo@netscout.com>
Cc: Kompella V, Purnima <Kompella.Purnima@commscope.com>; users@dpdk.org
Subject: Re: tailqs issue

External Email: This message originated outside of NETSCOUT. Do not click links or open attachments unless you recognize the sender and know the content is safe.

On Tue, 25 Mar 2025 22:24:33 +0000
"Lombardo, Ed" <Ed.Lombardo@netscout.com> wrote:

> Hi Stephen,
> I am building the dpdk-simple_mp example in meson/ninja.
>
> Our application is built in our custom build environment, and we are not using DPDK shared libraries, but are linking to DPDK static libs.
>
>  Thanks,
> Ed


Both need to be built the same way.