DPDK usage discussions
 help / color / mirror / Atom feed
From: "Pathak, Pravin" <pravin.pathak@intel.com>
To: Kiran Khatke <kirankhatke23may@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: RE: Memory sharing between two primary processes
Date: Mon, 6 Jun 2022 12:58:03 +0000	[thread overview]
Message-ID: <BL1PR11MB5461A9EF5F7E179A2E8DDB07F4A29@BL1PR11MB5461.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAGKgC8XJnQ2sjj-c3Yq+nJ8STvdVtMXyg-iG-Gfb-3g9PvXF+g@mail.gmail.com>

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

Hi Kiran –
Can your application create and manage shared memory on it own without using DPDK support ?
Regards
Pravin

From: Kiran Khatke <kirankhatke23may@gmail.com>
Sent: Monday, June 6, 2022 2:26 AM
To: users@dpdk.org
Subject: Memory sharing between two primary processes


Hi,



Per DPDK Multiprocess, we know that, it is possible to share memory(hugepages) between a primary and secondary Process.  Primary process allocates the memory and that is accessible by the secondary (both are using same  "--file-prefix=" parameter).



There is a need in our application, to have two primary processes (started with different file-prefix) and would like to know the options - To share memory (hugepage) between two primaries and which can give us better throughputs.



During exploration, got to know about memif PMD, which allows for DPDK and any other client using memif (DPDK, libmemif) to communicate over shared memory.

Do you have any comments about memif performance ? Are there better options over memif to share memory between two primaries ?



Thanks ,

Kiran

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

  reply	other threads:[~2022-06-06 12:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06  6:26 Kiran Khatke
2022-06-06 12:58 ` Pathak, Pravin [this message]
2022-06-06 13:24   ` Kiran Khatke
2022-06-06 13:53     ` Pathak, Pravin
2022-06-06 13:56       ` Kiran Khatke
2022-06-08  0:21         ` Pathak, Pravin
2022-06-08 18:54           ` Kiran Khatke

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=BL1PR11MB5461A9EF5F7E179A2E8DDB07F4A29@BL1PR11MB5461.namprd11.prod.outlook.com \
    --to=pravin.pathak@intel.com \
    --cc=kirankhatke23may@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).