DPDK usage discussions
 help / color / mirror / Atom feed
From: Cliff Burdick <shaklee3@gmail.com>
To: Staffan Wiklund <staffan491@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: Can the DPDK multi-process feature be used in Docker containers?
Date: Wed, 17 Nov 2021 22:11:19 -0800
Message-ID: <CA+Gp1naSb+VVruxdx30m+hL3XXqj8KhmUvEsgSgfCEZfuUDArg@mail.gmail.com> (raw)
In-Reply-To: <CAAV4wTjtoodzxAHVr_E3C56ecNvpXJGViaZf0+i3qDwzb8OX-g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

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 <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
>
>
>

[-- Attachment #2: Type: text/html, Size: 2356 bytes --]

  reply	other threads:[~2021-11-18  6:11 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 [this message]
2021-11-18  6:20   ` Li Feng
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=CA+Gp1naSb+VVruxdx30m+hL3XXqj8KhmUvEsgSgfCEZfuUDArg@mail.gmail.com \
    --to=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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git