From: Thomas Monjalon <thomas@monjalon.net>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Two DPDK instances in same Linux Process
Date: Wed, 13 Nov 2024 18:36:46 +0100 [thread overview]
Message-ID: <10686216.nUPlyArG6x@thomas> (raw)
In-Reply-To: <CH3PR01MB8470D40F4F6758434F7F9A888F5A2@CH3PR01MB8470.prod.exchangelabs.com>
13/11/2024 18:20, Lombardo, Ed:
> Hi,
> I have a situation where our NIC driver uses DPDK 22.11 and comes up and process packets. We added Suricata to our application and it also uses DPDK 22.11. Both the driver and Suricata are in the same Linux process. When the Suricata application starts and initializes DPDK with their own EAL init call it fails. I tried setting the driver DPDK as the primary and the Suricata as the secondary but still fails.
>
> The driver DPDK initialization occurs before the Suricata DPDK initialization.
>
> Also the driver DPDK has its own hugepages and Suricata has its own hugepages.
>
> What is the proper way to accommodate two DPDK instances in the same Linux application process?
1 application must call rte_eal_init() only once.
I wonder how you can integrate Suricata into your application.
Isn't it a standalone application?
prev parent reply other threads:[~2024-11-13 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 17:20 Lombardo, Ed
2024-11-13 17:36 ` Thomas Monjalon [this message]
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=10686216.nUPlyArG6x@thomas \
--to=thomas@monjalon.net \
--cc=Ed.Lombardo@netscout.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).