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 00BC8A0509 for ; Thu, 14 Apr 2022 21:57:04 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8E2994067E; Thu, 14 Apr 2022 21:57:04 +0200 (CEST) Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) by mails.dpdk.org (Postfix) with ESMTP id 10C6E4067C for ; Thu, 14 Apr 2022 21:57:03 +0200 (CEST) Received: by mail-lf1-f42.google.com with SMTP id b21so10920745lfb.5 for ; Thu, 14 Apr 2022 12:57:03 -0700 (PDT) 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=Mj+8i5xV/eyC7rkesMmx6VELUDVD24FaUeNmlshzadA=; b=JgFzUJv1qmby6EojVWgxmO3oBuVIleT7UeU5I6mGU4wNT8ooGJqdJZV1Ud4j5x0BX9 GiDZPqxEuPmCVrZtIdsoQI3ZpTTeN7pls+tnKb5MG/sdSAevgaiPrhrw3pYwgfDPi3Mo pGo4NWmKhaNvyqnJ77bEJljA1IZqu1idiQH/xgyBdPBqM9r0NgnJc3pQjHGNMR7xIweC h/Qx411KlwKrQp31ZJRCo7CPGN92dvYlYvXODfu/f8o9Dlkn/Dky8uE49ct47+vwKrJF FejdqjGwO2/n7dKv6jYVZkp7NN57krSn+eh7cguaVYnZdUAbCRalXy2MYCSuqXsKNfCi ef0Q== 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=Mj+8i5xV/eyC7rkesMmx6VELUDVD24FaUeNmlshzadA=; b=6Kmhj0y98+gUsaCCyJqKuDWGlL7OOedbxd3CNRon22x6k1Kntiscdz3M2EdYmYS2Ow sa5Qlu8yTc3fNy20s7TFoe6lI6ExP9Fyw1zxm0gfNpElUnP3Pf9NxKqxTcz4eqHKwXU4 57t3ft6o1h05WQkIy42ph//sHi83l0krBuyXHhK0c7mIMuCUi/jLPLmL7/2VwONAtdsK deuCAtmWkeoCZRcNiTLtFIzNIstkOFcTcpM8qm1s8QzOwAtZY5wryoud40lgWM1iEQGb /gbQHniZhg70/NEYWbnstqhlN4bsKUwl3gr45lxA2sXuNuwYZqfk6fSjcpOYFIEbS769 vCdw== X-Gm-Message-State: AOAM5332TZhINQCSq7nb0VhZx2b/u5NoXBbPeyKVqV0NwS4/ldPaB77t sVK9GwB223Q7BdU/k9JqNgnUYYtclfthkzTMFqRnsg2Q6OQ= X-Google-Smtp-Source: ABdhPJyWChydB0FrwRTuokLVzlEYl6Et62AG8/0UmcPqFL9zM9HBk7qwx4SvVHLyOT5UWnQOt6fsInZ4QyoD03yTJ3g= X-Received: by 2002:a19:6b13:0:b0:46b:b970:5792 with SMTP id d19-20020a196b13000000b0046bb9705792mr2972336lfa.100.1649966222189; Thu, 14 Apr 2022 12:57:02 -0700 (PDT) MIME-Version: 1.0 From: Antonio Di Bacco Date: Thu, 14 Apr 2022 21:56:50 +0200 Message-ID: Subject: Best practice to share memory between two DPDK processes in different docker containers To: users@dpdk.org Content-Type: multipart/alternative; boundary="00000000000090a78b05dca2b2dc" 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 --00000000000090a78b05dca2b2dc Content-Type: text/plain; charset="UTF-8" I imagine that there should be a way of sharing memory between two DPDK processes running in different docker containers. Probably the two DPDK processes could mmap the same hugepage? Probably we could pass pid and fd from one process to the other and (bypassing pid namespaces) be able to mmap the same memory? I wonder if DPDK architects thought about this scenario. --00000000000090a78b05dca2b2dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I imagine that there should be a way of sharing memory bet= ween two DPDK processes running in different docker containers. Probably th= e two DPDK processes could mmap the same hugepage? Probably we could pass p= id and fd from one process to the other and (bypassing=C2=A0pid namespaces)= be able to mmap the same memory?
I wonder if DPDK architects thought a= bout this scenario.


--00000000000090a78b05dca2b2dc--