DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nissim Nisimov <NissimN@Radware.com>
To: "'dev@dpdk.org'" <dev@dpdk.org>
Subject: [dpdk-dev] propose a solution for mapping same virtual address space to asymmetric processes
Date: Tue, 13 Oct 2015 15:40:02 +0000	[thread overview]
Message-ID: <94AA676E9B9A384A844E7692F3CAD906C54F645D@ILMB2.corp.radware.com> (raw)

Hi all,

The below will try to suggest a modification to the initialization of Environment Abstraction Layer (AKA EAL) so it will be able to allocate memory zones from same virtual memory addresses even if the primary process is not similar to the secondary processes.

Problem:
The DPDK Primary/Secondary model requires that the exact same hugepage memory mappings be present in all applications.
An issue may occur when the Primary and secondary processes are not symmetric in such way that the code has big differences (for example, Primary process is a traffic distributer and secondary is a worker).
The result may be that specific virtual address region in the first process won't be available in the second process.


Suggested solution:
Map all related rte and uio sections somewhere close to the end of huge pages memory (that mean rte_eal_memory_init() should be called before rte_config_init() in primary process)
According to our observations there will be more probability to success when allocating the above sections after huge pages section (actually uio is already allocated after the huge pages area)

It solved our problem when trying to work with a primary traffic distributer which is a very "light" process and few secondary worker processes.


Please share your thoughts on this before I will try to commit our patch for review

Thanks,
Nissim

             reply	other threads:[~2015-10-13 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 15:40 Nissim Nisimov [this message]
2015-10-13 15:49 ` Richardson, Bruce
2015-10-13 17:26   ` Nissim Nisimov

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=94AA676E9B9A384A844E7692F3CAD906C54F645D@ILMB2.corp.radware.com \
    --to=nissimn@radware.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).