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 340B1A0C56 for ; Fri, 26 Nov 2021 13:27:53 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A429F40C35; Fri, 26 Nov 2021 13:27:52 +0100 (CET) Received: from mail-vk1-f176.google.com (mail-vk1-f176.google.com [209.85.221.176]) by mails.dpdk.org (Postfix) with ESMTP id 9CF7F406FF for ; Fri, 26 Nov 2021 13:27:51 +0100 (CET) Received: by mail-vk1-f176.google.com with SMTP id 84so5841023vkc.6 for ; Fri, 26 Nov 2021 04:27:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=+PDX8M+kTVdY+0S5C2qVYoJLo20sdvqJ2c6e8/pkryE=; b=WMiS2htImEwhef066xNSpRVTwkQ1YjxTDT3ilZ3uykMsLsBD+Zalm9SP/3uhzc8Vpy 389hU+iuNTIlzY4dTwRDAbo2LgKzzbPrVcbOn2h5CbHo5SkMvHafretjA+x3J3/FRhVy YWdr7gGA5vMhxzqP/By9mu0kvtGa723HOkZh8t4BVhzWUfmOZSYkvx5V8qOQw/kBCwRx 4CzI8lNCcN0EkMN+O5Hf4jkJ+ODaBWDE2HuwtzuW2RGNzcxgVnR1fnXXoPSRhkg/ULbN NpWl4o4uMF9p46xEfb3o/Y9M447jB1oscrZnayLRHO2a29L3zTyfN1qEVeKMM1Vfysng 28gA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+PDX8M+kTVdY+0S5C2qVYoJLo20sdvqJ2c6e8/pkryE=; b=IT1zRxUgfmZfCP5NHiqwiveGfToSKRsDVFtgVSQ6T0Wr1HRkds/7OFJtyKlr4/vj8a GLETbZXFNqZ/RwpdsNQdrWgfQQTgkIWwnhJzp9SeCFhb45xdBQmIQcuFeF8oh4AJnvjF 4pk/McAHivKZqoqef1Ks255rpBkqX8ATNgaNiMbtqHb+CtPaYtf5ZEXAyf/sTwAyANBk CU6QKtxJCSBGUIzccNVHc3ULmw4M6QMXgBw09V6TZoAmGEH/0+H3k69cKn6AGiinhwTh hpaW6yjMdkLMcfOROKI+L391kVGOfHwPcLQ0uN8tOO1jlmFzMbQFn8Z75TtbxRj55D8d OkXA== X-Gm-Message-State: AOAM531DaHsjgUcVF4IEmLIr8tFoM6qGUp2lQHpglqcUudm2xK4StwxE WLmrrnWzVHS4jOp05qrJ1icCQSEg2om3COfWpY26fDg0Igw= X-Google-Smtp-Source: ABdhPJwdncjecA5cqGCgv62nHgGF8xNU1mk8E/8XfK20Au2MmYws37CpgDPZdhWzy7qpWVZkRn2SPgGRxloRQI8g4K8= X-Received: by 2002:a1f:e605:: with SMTP id d5mr13301451vkh.39.1637929670734; Fri, 26 Nov 2021 04:27:50 -0800 (PST) MIME-Version: 1.0 From: Staffan Wiklund Date: Fri, 26 Nov 2021 13:27:40 +0100 Message-ID: Subject: Impact on DPDK application when using the multi-process feature? To: users Content-Type: multipart/alternative; boundary="00000000000030f81305d1b038d4" 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 --00000000000030f81305d1b038d4 Content-Type: text/plain; charset="UTF-8" Hello I wonder if you please can help me with some questions regarding the DPDK multi-process feature? If a primary process and the secondary processes all execute on different CPU cores, what limitations are there on the secondary processes when using DPDK functions for initialization of EAL and for handling ethernet devices? That is, is a secondary process allowed to call the rte_eal_init function or any of the rte_eth_xxx functions? What will happen if a secondary process calls any of these DPDK functions? The reason for these questions is that I would like to execute 3-4 DPDK applications that now executes as stand-alone applications as one primary process and the other applications as secondary processes. All these processes will share memory which shall be used to improve the speed of communication between the applications. The applications currently use DPDK for Ethernet based communication and I would like to learn what needs to be modified in order to be able to execute them as a primary and secondary processes using DPDK shared memory. Best regards Staffan --00000000000030f81305d1b038d4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello

I wonder if you please= can help me with some questions regarding the DPDK multi-process feature?<= /div>

If a primary process and the secondary processes a= ll execute on different CPU cores,
what limitations are there on = the secondary processes when using DPDK functions
for initializat= ion of EAL and for handling ethernet devices?

That= is, is a secondary process allowed to call the rte_eal_init function or an= y of
the rte_eth_xxx functions?
What will happen if a s= econdary process calls any of these DPDK functions?

The reason for these questions is that I would like to execute 3-4 DPDK a= pplications that
now executes as stand-alone applications as= one primary process and the other
applications as secondary= processes. All these processes will share memory which
shall be = used to improve the speed of communication between the applications.
<= div>
The applications currently use DPDK for Ethernet based c= ommunication and I would
like to learn what needs to be modified = in order to be able to execute them as a
primary and secondary pr= ocesses using DPDK shared memory.

Best regards=
Staffan
--00000000000030f81305d1b038d4--