DPDK usage discussions
 help / color / mirror / Atom feed
From: Li Feng <fengli@smartx.com>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: Staffan Wiklund <staffan491@gmail.com>, users <users@dpdk.org>
Subject: Re: Can the DPDK multi-process feature be used in Docker containers?
Date: Thu, 18 Nov 2021 14:20:13 +0800	[thread overview]
Message-ID: <CAHckoCyFJ+D2qHqX5TZQbnpBA+TF_-K5_JxE-GBoh78ndVUqGw@mail.gmail.com> (raw)
In-Reply-To: <CA+Gp1naSb+VVruxdx30m+hL3XXqj8KhmUvEsgSgfCEZfuUDArg@mail.gmail.com>

On Thu, Nov 18, 2021 at 2:11 PM Cliff Burdick <shaklee3@gmail.com> wrote:
>
> 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.
>
By the way, if I want to run two separate dpdk processes in two
different dockers, what should I do?
e.g. Running two processes: examples/dpdk-mp_server
These two dockers have mapped the same /dev/hugepages directories.
I have tested, the dpdk will crash because the hugepages are mixed.

Thanks.
>
> On Wed, Nov 17, 2021, 05:58 Staffan Wiklund <staffan491@gmail.com> 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:
>> <build_dir>/examples/dpdk-mp_server -l 1-2 -n 4 -- -p 3 -n 2
>>
>> and the DPDK example mp_client executes in another Docker container:
>>
>> <build_dir>/examples/dpdk-mp_client -l 3 -n 4 --proc-type=auto -- -n 0
>>
>> Is this possible to implement?
>>
>> Thanks
>> Staffan
>>
>>

  reply	other threads:[~2021-11-18  6:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 13:47 Staffan Wiklund
2021-11-18  6:11 ` Cliff Burdick
2021-11-18  6:20   ` Li Feng [this message]
2021-11-18  6:23     ` Cliff Burdick
2021-11-18  6:47       ` Li Feng
2021-11-18  7:12         ` Staffan Wiklund
2021-11-18 17:38           ` Cliff Burdick

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=CAHckoCyFJ+D2qHqX5TZQbnpBA+TF_-K5_JxE-GBoh78ndVUqGw@mail.gmail.com \
    --to=fengli@smartx.com \
    --cc=shaklee3@gmail.com \
    --cc=staffan491@gmail.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).