DPDK usage discussions
 help / color / mirror / Atom feed
From: "hom.sepanta@gmail.com" <hom.sepanta@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Using memzone for sharing memory
Date: Sun, 6 May 2018 16:34:45 +0430	[thread overview]
Message-ID: <CAG8BTKnq6dYOhH45eNGXLk-a5vaAiFaFxJwSto04DwKXedZMzw@mail.gmail.com> (raw)

Hi everyone. I was wondering if the virtual address of memzones remains the
same across different processes. The memzone docs mention the same physical
address is returned but there is no mention of the virtual address. A
little bit of testing makes it look like that the virtual address is also
the same, but I can't be sure about that.

The interesting thing about this for me is that if the same virtual address
is always returned, I could store and share complex data structures with
internal pointers in a memzone.

Does this sound possible? If using memzones is not the correct approach for
this, could you suggest another course of action?

Cheers,
Mostafa

             reply	other threads:[~2018-05-06 12:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-06 12:04 hom.sepanta [this message]
2018-05-08 13:07 ` Wiles, Keith

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=CAG8BTKnq6dYOhH45eNGXLk-a5vaAiFaFxJwSto04DwKXedZMzw@mail.gmail.com \
    --to=hom.sepanta@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).