From: Cliff Burdick <shaklee3@gmail.com>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: Best practice to share memory between two DPDK processes in different docker containers
Date: Fri, 15 Apr 2022 07:52:20 -0700 [thread overview]
Message-ID: <CA+Gp1nZCkHisqVqWrzLB0ZG-XfFMXLtfrBCB8re=ja5o+DpOAg@mail.gmail.com> (raw)
In-Reply-To: <CAO8pfFn5GYsjdVVZK9TUVGNZKTJBfckAAOBC=jHiosiuE5aEQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
Hi Antonio, see this discussion:
http://mails.dpdk.org/archives/users/2021-November/006014.html
On Thu, Apr 14, 2022 at 12:57 PM Antonio Di Bacco <a.dibacco.ks@gmail.com>
wrote:
> 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: 1020 bytes --]
prev parent reply other threads:[~2022-04-15 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 19:56 Antonio Di Bacco
2022-04-15 14:52 ` Cliff Burdick [this message]
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+Gp1nZCkHisqVqWrzLB0ZG-XfFMXLtfrBCB8re=ja5o+DpOAg@mail.gmail.com' \
--to=shaklee3@gmail.com \
--cc=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).