From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5EBE745CF9 for ; Wed, 13 Nov 2024 18:36:51 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 413F740B8F; Wed, 13 Nov 2024 18:36:51 +0100 (CET) Received: from fout-b7-smtp.messagingengine.com (fout-b7-smtp.messagingengine.com [202.12.124.150]) by mails.dpdk.org (Postfix) with ESMTP id 0322B406BC for ; Wed, 13 Nov 2024 18:36:49 +0100 (CET) Received: from phl-compute-12.internal (phl-compute-12.phl.internal [10.202.2.52]) by mailfout.stl.internal (Postfix) with ESMTP id 3637911400FB; Wed, 13 Nov 2024 12:36:49 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-12.internal (MEProxy); Wed, 13 Nov 2024 12:36:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1731519409; x=1731605809; bh=MwdKPTV2+Mzc6Aqc5xpnt6ooOecJYyj1iINhB2rnPKM=; b= e2Mrg1GW2J0o3dmYMs988JDcORcz53aKw4iYUmVjoYRTuDE6MJmfUUiwkUy1Cj/y epg/gsl6k8U+dXjRCznDMTHG0roCuegMAfpAhE1dinUrlZWttqgHVYSWUST4cfFn Zd9VIGdWb6de8ph3bun2V7lwuh0bxrcXHhQNEpR+avPlxgLMcsPB7tlSQRYthxCH YomV1vOne83OqH2jynsYWjfbtCZGvHS7ROfzelX9wMO4OWzmRzy1tTGhqM7aLv8i oX74H0VC0L5z3GXcKJuQE9CfLAv4C25X94rZL4frkkuF35KR0AVhLyhewISsNOrd uk5OFKxNKvhsj5KUuNMoCg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1731519409; x= 1731605809; bh=MwdKPTV2+Mzc6Aqc5xpnt6ooOecJYyj1iINhB2rnPKM=; b=D /xjVEaze/J0fYenz0TsuM0Gz9bRYc9QCbvixuefbo6Wwj9dMsT7h3OnLkl+yk2In ssbKLpM73ZKwFjjKJL3NziHgkI844hC0f92wVTYwvWkPVWfl+3eHyZ/ZYfi1Zg1v CCTZD+k1KYFN4bkdwC7XDPzwEA+kbQCYCiMDCQYjA1rh5zKnNckQDk0aosEuLds3 FXLKnm1LHYoaSQim6kSBLva6+c+jG1Rc3i1bpeaZymqutQ4q+jl7iVvxvG1hPQKf afaiQQxH1yB7TcFP8HnjSvmjTaXCp/vUt3TMx5ZWLuEfL9SHnv2p15XEGN33mG8p IhdJ/0ZVIxqscf2I5cxdA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrvddtgddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhephffvvefufffkjghfggfgtgesthfuredttddtjeen ucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrg hlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeejudevheeiveduuddtveffgfdtgeek ueevjeffjeegtdeggeekgfdvuefgfeekjeenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtpdhn sggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopegvugdrlh homhgsrghrughosehnvghtshgtohhuthdrtghomhdprhgtphhtthhopehushgvrhhssegu phgukhdrohhrgh X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 13 Nov 2024 12:36:48 -0500 (EST) From: Thomas Monjalon To: "Lombardo, Ed" Cc: "users@dpdk.org" Subject: Re: Two DPDK instances in same Linux Process Date: Wed, 13 Nov 2024 18:36:46 +0100 Message-ID: <10686216.nUPlyArG6x@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org 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?