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 83E35A0C41 for ; Thu, 18 Nov 2021 07:11:32 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0A7A040687; Thu, 18 Nov 2021 07:11:32 +0100 (CET) Received: from mail-ua1-f45.google.com (mail-ua1-f45.google.com [209.85.222.45]) by mails.dpdk.org (Postfix) with ESMTP id 4CC6640395 for ; Thu, 18 Nov 2021 07:11:30 +0100 (CET) Received: by mail-ua1-f45.google.com with SMTP id o1so11352508uap.4 for ; Wed, 17 Nov 2021 22:11:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NJ4lCImxMzPEl2hOEdhO44i+gOzBCHmJXMyO8OqpQnw=; b=O9eDnKDxitNplvNT09YCpHdbeAmv5hlgPu1MQNuJNITaTTEnOLaj+ZW6334H83oMH1 ZsBh+BFj3Rps0ELFpDrmWRgG1VhoRHhUdQyXBk0EvuZd9RVgczW85yjVrPBrsIyWIwgQ YAnzUssinEF4scBq/9Z7NMncBLzcIvGaKyOcE1qu7QgSKoRh9XQX6lC3fD0IjsEZZYfp AFzVFRd8Wa9KS6rei79t8NTWl2Bs1Eh4Kzka/da4GClih2ZnlvZfEOKo+GvDfSg6QH84 9jnHHgyYghrHGGmJixm7SZjz5dd96zWSSO54TzZyuvQ1RpqwmAyKEXTmtvjGqPl4arxu etEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NJ4lCImxMzPEl2hOEdhO44i+gOzBCHmJXMyO8OqpQnw=; b=gExwEiTeTPVgmg3He4gPh3VPxVBQkr0W7ATzo8mgQDaaziJUKJ6ZyZMHEpcb3ZM3X0 amJ1cbGVFZVfIEGVlqmreUC9ndzxQSLuZEl04qPwMRgG17mvmQbltqdNzL9mAbJrCCHe Za3sIymta3MVsawqxf/6X03WmZKuHnSXcDouV1BLFmXM1IHC4tAa/4joORBQ0FuuTCbz 2TU9tT8sIBrnc5QnuaXVQhaR5INaHIb8q9yCavBlRxFfi+erOpzy9PbIBqPlBR8zRoiC kliIZjRe3ophCHfc8GaMKAP6PbrxCmkgHI5WKIxCmXEWb34+Xp3/y/35XThaqy2DZOV5 ZsyQ== X-Gm-Message-State: AOAM531bUWxr3vaSGHgyp/GdUNbYBJ7JiY3zPDaXC8ID/bPUzzZLnZzV UqjLp+KoBLGBCVBbLfxnWIbWVF+FsEG8ZA6NFl8= X-Google-Smtp-Source: ABdhPJy+azM1DKcPLMspq8PRUDGl8HTWmzaUkLAryWhO9UEoafjRbd9XneyrOSnFuMD3xEW/nV33hersKJ0WwmMz0NQ= X-Received: by 2002:a05:6102:cd3:: with SMTP id g19mr79148689vst.14.1637215889532; Wed, 17 Nov 2021 22:11:29 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Cliff Burdick Date: Wed, 17 Nov 2021 22:11:19 -0800 Message-ID: Subject: Re: Can the DPDK multi-process feature be used in Docker containers? To: Staffan Wiklund Cc: users Content-Type: multipart/alternative; boundary="000000000000842bb105d10a074b" 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 --000000000000842bb105d10a074b Content-Type: text/plain; charset="UTF-8" Yes. Try mapping the dpdk metadata directory (/var/run/dpdk) into both containers from the host. You should be able to do the normal dual process methods. On Wed, Nov 17, 2021, 05:58 Staffan Wiklund wrote: > Hello > > I wonder if it is possible to use the DPDK multi-process feature in Docker > containers? > > That is, can a DPDK application execute in a Docker container and share its > DPDK memory with another DPDK application executing in another Docker > container > using the DPDK multi-process feature? > > For example if the DPDK example mp_server executes in one Docker container: > /examples/dpdk-mp_server -l 1-2 -n 4 -- -p 3 -n 2 > > and the DPDK example mp_client executes in another Docker container: > > /examples/dpdk-mp_client -l 3 -n 4 --proc-type=auto -- -n 0 > > Is this possible to implement? > > Thanks > Staffan > > > --000000000000842bb105d10a074b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes. Try mapping the dpdk metadata directory (/var/run/dp= dk) into both containers from the host. You should be able to do the normal= dual process methods.


On Wed, Nov 17, 2021, 05:= 58 Staffan Wiklund <staffan491@g= mail.com> wrote:
Hello

= I wonder if it is possible to = use the DPDK multi-process feature in Docker containers?
<= span style=3D"font-family:arial,sans-serif">
That is, can a DPDK application execute= in a Docker container and share its
DPDK memory with another DPDK application executing= in another Docker container
using the DPDK multi-process feature?
=
For example if the DPDK example mp_ser= ver executes in one Docker container:
<build_dir>/examples/dpdk-mp_server -l 1-2 -n 4 -- -p 3 -n 2

and the DPDK example mp_cli= ent executes in another Docker container:
=
<build_dir>/examples/dpd=
k-mp_client -l 3 -n 4 --proc-type=3D=
auto -- -n 0

Is this =
possible to implement?

Thanks
Staffan

--000000000000842bb105d10a074b--