From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Fastest and easiest method to share mem between two DPDK processes
Date: Mon, 4 Apr 2022 23:52:12 +0300 [thread overview]
Message-ID: <20220404235212.23b49d44@sovereign> (raw)
In-Reply-To: <CAO8pfFmkQwhCH8SGJaBVaeDbSNLd3WTo0Uy+3O-r5RkZq5bYfA@mail.gmail.com>
2022-04-04 21:48 (UTC+0200), Antonio Di Bacco:
> Il giorno lun 4 apr 2022 alle ore 18:10 Dmitry Kozlyuk <
> dmitry.kozliuk@gmail.com> ha scritto:
>
> > 2022-04-04 16:04 (UTC+0200), Antonio Di Bacco:
> > > I have a Primary (Pa) and a secondary (Sa). Pa allocates memory that
> > shares
> > > with Sa.
> > > Now I also have another Primary (Pb). I need to allocate some memory in
> > Pa
> > > or Sa that has to be shared with (Pb) or the reverse. Is this a feasible
> > > configuration?
> >
> > Please tell more about the use case.
> > Do you want to share an arbitrary block or part of DPDK memory?
> > What the shared memory contains and how it will be used w.r.t. DPDK?
> >
>
> The memory will contain some signal samples, we would like the samples to
> be on a hugepage (1GB) shared between Sa and Pb.
> Sa will write and Pb will read.
Have you considered memif PMD (that you are already familiar with)?
It's precisely shared memory between processes.
And a shared hugepage(s) for data is how it operates in zero-copy mode.
prev parent reply other threads:[~2022-04-04 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 14:04 Antonio Di Bacco
2022-04-04 16:10 ` Dmitry Kozlyuk
2022-04-04 19:48 ` Antonio Di Bacco
2022-04-04 20:52 ` Dmitry Kozlyuk [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=20220404235212.23b49d44@sovereign \
--to=dmitry.kozliuk@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).