DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Kamaraj P <pkamaraj@gmail.com>, Kevin Traynor <ktraynor@redhat.com>
Cc: dev@dpdk.org, Nageswara Rao Penumarthy <npenumar@cisco.com>,
	"Kamaraj P (kamp)" <kamp@cisco.com>
Subject: Re: [dpdk-dev] CONFIG_RTE_MAX_MEM_MB fails in DPDK18.05
Date: Wed, 19 Feb 2020 14:23:27 +0000	[thread overview]
Message-ID: <56527d9f-b079-a580-4a80-2207c1822260@intel.com> (raw)
In-Reply-To: <CAG8PAarXLqdOiMFGY7mptW8T5hE8-=GK-3DLCuSgqnuVuNELeQ@mail.gmail.com>

On 19-Feb-20 11:16 AM, Kamaraj P wrote:
> Hi Kevin/Anatoly,
> 
> Yes we have the patch already included in our code base.
> 
> Looks like it get struck in the below piece of the code:
> mapped_addr = mmap(requested_addr, (size_t)map_sz, PROT_READ,
>                                  mmap_flags, -1, 0);
> 
> Could you please share your thoughts on this?
> 
> Thanks,
> Kamaraj
> 

Hi,

If it's stuck mapping, that probably means it is pinning the memory. Did 
you call mlockall() (or equivalent) before EAL initialization?

-- 
Thanks,
Anatoly

  reply	other threads:[~2020-02-19 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07 17:01 Kamaraj P
2019-12-10 10:23 ` Burakov, Anatoly
2020-02-17  9:57   ` Kamaraj P
2020-02-19 10:23     ` Burakov, Anatoly
2020-02-19 10:56       ` Kevin Traynor
2020-02-19 11:16         ` Kamaraj P
2020-02-19 14:23           ` Burakov, Anatoly [this message]
2020-02-19 15:02             ` Kamaraj P
2020-02-19 15:28               ` Burakov, Anatoly
2020-02-19 15:42                 ` Kamaraj P
2020-02-19 16:00                   ` Burakov, Anatoly
2020-02-19 16:20                     ` Kamaraj P
2020-02-20 10:02                       ` 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=56527d9f-b079-a580-4a80-2207c1822260@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=kamp@cisco.com \
    --cc=ktraynor@redhat.com \
    --cc=npenumar@cisco.com \
    --cc=pkamaraj@gmail.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).