From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Kamaraj P <pkamaraj@gmail.com>
Cc: Kevin Traynor <ktraynor@redhat.com>,
dev@dpdk.org, Nageswara Rao Penumarthy <npenumar@cisco.com>,
"Kamaraj P (kamp)" <kamp@cisco.com>,
mtang2@cisco.com
Subject: Re: [dpdk-dev] CONFIG_RTE_MAX_MEM_MB fails in DPDK18.05
Date: Thu, 20 Feb 2020 10:02:14 +0000 [thread overview]
Message-ID: <a2ef0c2d-d5c6-2f56-4b2b-2d7b80807376@intel.com> (raw)
In-Reply-To: <CAG8PAaowDOvWkeA0FUbUHz4UB85afhwnT7Wca0Asq4Q2YDeE-g@mail.gmail.com>
On 19-Feb-20 4:20 PM, Kamaraj P wrote:
> Hi Anatoly,
>
> Yes we are facing an issue with our custom applications.
> Earlier we have tried with l2fwd DPDK application and does not see any
> issue with memory initialization.
> Not sure whether we missed any other options.
>
> BTW when we tried with l2fwd application, the application does not seem
> to hang during the memory initialization where as our application is
> kind of struck when getting memory.
> Do we tune any config parameters from DPDK ?
> Please advise.
>
Hi,
This doesn't look like an issue that is with DPDK. It is more likely
that something else triggers this (similar to mlockall()). Are you sure
there are no more mem lock calls anywhere in your application before EAL
init (i.e. inside the libraries you use, etc.)? Because so far, page
pinning is the only thing i can think of that would cause this sort of
behavior.
--
Thanks,
Anatoly
prev parent reply other threads:[~2020-02-20 10:02 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
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 [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=a2ef0c2d-d5c6-2f56-4b2b-2d7b80807376@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=kamp@cisco.com \
--cc=ktraynor@redhat.com \
--cc=mtang2@cisco.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).