From: Eli Britstein <eli.britstein@toganetworks.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] ivshmem mmap to specific address
Date: Wed, 9 Dec 2015 06:52:56 +0000 [thread overview]
Message-ID: <AM2PR02MB260F081AA5A18F6CFCDC6F783E80@AM2PR02MB260.eurprd02.prod.outlook.com> (raw)
Hello,
In librte_eal, in eal_ivshmem.c, in function map_all_segments, there is mapping of segments from the metadata to the same virtual address as written in the metadata.
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?
Thanks,
Eli
-------------------------------------------------------------------------------------------------------------------------------------------------
This email and any files transmitted and/or attachments with it are confidential and proprietary information of
Toga Networks Ltd., and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager. This message contains confidential
information of Toga Networks Ltd., and is intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately
by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not
the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited.
------------------------------------------------------------------------------------------------------------------------------------------------
next reply other threads:[~2015-12-09 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 6:52 Eli Britstein [this message]
2015-12-09 10:38 ` Burakov, Anatoly
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=AM2PR02MB260F081AA5A18F6CFCDC6F783E80@AM2PR02MB260.eurprd02.prod.outlook.com \
--to=eli.britstein@toganetworks.com \
--cc=dev@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).