From: Stephen Hemminger <stephen@networkplumber.org>
To: "Kompella V, Purnima" <Kompella.Purnima@commscope.com>
Cc: "Lombardo, Ed" <Ed.Lombardo@netscout.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: tailqs issue
Date: Wed, 26 Mar 2025 07:14:16 -0700 [thread overview]
Message-ID: <20250326071416.4f7a2394@hermes.local> (raw)
In-Reply-To: <DM6PR14MB35970ED0AEDE913BB270ABC69CA62@DM6PR14MB3597.namprd14.prod.outlook.com>
On Wed, 26 Mar 2025 10:27:40 +0000
"Kompella V, Purnima" <Kompella.Purnima@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.
next prev parent reply other threads:[~2025-03-26 14:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 17:50 Lombardo, Ed
2025-03-19 20:23 ` Stephen Hemminger
2025-03-19 21:52 ` Lombardo, Ed
2025-03-19 23:16 ` Stephen Hemminger
2025-03-21 18:18 ` Lombardo, Ed
2025-03-24 5:01 ` Lombardo, Ed
2025-03-24 14:59 ` Kompella V, Purnima
2025-03-24 16:39 ` Lombardo, Ed
2025-03-25 10:25 ` Kompella V, Purnima
2025-03-25 14:39 ` Lombardo, Ed
2025-03-25 22:20 ` Stephen Hemminger
2025-03-25 22:24 ` Lombardo, Ed
2025-03-25 22:41 ` Stephen Hemminger
2025-03-25 22:56 ` Lombardo, Ed
2025-03-26 10:27 ` Kompella V, Purnima
2025-03-26 14:14 ` Stephen Hemminger [this message]
2025-03-26 14:33 ` Kompella V, Purnima
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250326071416.4f7a2394@hermes.local \
--to=stephen@networkplumber.org \
--cc=Ed.Lombardo@netscout.com \
--cc=Kompella.Purnima@commscope.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).