DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gooch, Stephen" <stephen.gooch@windriver.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] mmap() hint address
Date: Fri, 13 Jun 2014 21:02:33 +0000	[thread overview]
Message-ID: <9205DC19ECCD944CA2FAC59508A772BABCEFF60C@ALA-MBA.corp.ad.wrs.com> (raw)

Hello,

I have seen a case where a secondary DPDK process tries to map uio resource in which mmap() normally sends the corresponding virtual address as a hint address.  However on some instances mmap() returns a virtual address that is not the hint address, and it result in rte_panic() and the secondary process goes defunct.

This happens from time to time on an embedded device when nr_hugepages is set to 128, but never when nr_hugepage is set to 256 on the same device.    My question is, if mmap() can find the correct memory regions when hugepages is set to 256, would it not require less resources (and therefore be more likely to pass) at a lower value such as 128?

Any ideas what would cause this mmap() behavior at a lower nr_hugepage value?

- Stephen

             reply	other threads:[~2014-06-13 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 21:02 Gooch, Stephen [this message]
2014-06-13 21:27 ` Richardson, Bruce
2014-06-16  8:00   ` Burakov, Anatoly
2014-06-20 14:36     ` Gooch, Stephen
2014-06-20 14:42       ` 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=9205DC19ECCD944CA2FAC59508A772BABCEFF60C@ALA-MBA.corp.ad.wrs.com \
    --to=stephen.gooch@windriver.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).