DPDK usage discussions
 help / color / mirror / Atom feed
From: Antonio Di Bacco <a.dibacco.ks@gmail.com>
To: users@dpdk.org
Subject: Best practice to share memory between two DPDK processes in different docker containers
Date: Thu, 14 Apr 2022 21:56:50 +0200	[thread overview]
Message-ID: <CAO8pfFn5GYsjdVVZK9TUVGNZKTJBfckAAOBC=jHiosiuE5aEQQ@mail.gmail.com> (raw)

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

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.

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

             reply	other threads:[~2022-04-14 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 19:56 Antonio Di Bacco [this message]
2022-04-15 14:52 ` 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='CAO8pfFn5GYsjdVVZK9TUVGNZKTJBfckAAOBC=jHiosiuE5aEQQ@mail.gmail.com' \
    --to=a.dibacco.ks@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).