From: Stephen Hemminger <stephen@networkplumber.org>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: "Kompella V, Purnima" <Kompella.Purnima@commscope.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: tailqs issue
Date: Tue, 25 Mar 2025 15:20:06 -0700 [thread overview]
Message-ID: <20250325152006.00619b1f@hermes.local> (raw)
In-Reply-To: <CH3PR01MB8470FE1CC547BF2958A046BF8FA72@CH3PR01MB8470.prod.exchangelabs.com>
On Tue, 25 Mar 2025 14:39:08 +0000
"Lombardo, Ed" <Ed.Lombardo@netscout.com> wrote:
> Hi Purnima,
> I will try your suggestion, but this seems weird. What if I have a 3rd party application that I want to integrate with our application. This could be impossible to coordinate this requirement.
>
> Thanks,
> Ed
Primary and secondary are tightly coupled. They have to be built from same base, so true 3rd party
support would be very difficult.
How are you building? Using meson and DPDK process or something custom?
I seem to remember there was a issue long ago with shared libraries and build flags
where initializers would not get run unless a flag was passed during the shared library
link step.
next prev parent reply other threads:[~2025-03-25 22:20 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 [this message]
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
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=20250325152006.00619b1f@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).