DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Eli Britstein <eli.britstein@toganetworks.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ivshmem mmap to specific address
Date: Wed, 9 Dec 2015 10:38:21 +0000	[thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E45123697820B0DA1@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <AM2PR02MB260F081AA5A18F6CFCDC6F783E80@AM2PR02MB260.eurprd02.prod.outlook.com>

Hi Eli

> Is there a method to guarantee that this mapping won't fail, even for
> different processes, that might have large code or constructors running even
> before main?

I'm afraid there is none. That's the nature of the beast. The best you can do is map stuff into a different address range using --base-virtaddr flag in the primary process and hope that this time your "large code or constructors running before main" won't tread into that virtual address space. But even that is not a guarantee by any means.

Thanks,
Anatoly

      reply	other threads:[~2015-12-09 10:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  6:52 Eli Britstein
2015-12-09 10:38 ` Burakov, Anatoly [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=C6ECDF3AB251BE4894318F4E45123697820B0DA1@IRSMSX109.ger.corp.intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=eli.britstein@toganetworks.com \
    /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).