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: Wed, 19 Feb 2020 15:28:05 +0000 [thread overview]
Message-ID: <e88a771a-c7aa-9fe4-3934-091e18607e9f@intel.com> (raw)
In-Reply-To: <CAG8PAaoDGu40gSAJOErbciHG6ubyXx4SU_rNinV2Te8C4a6N3w@mail.gmail.com>
On 19-Feb-20 3:02 PM, Kamaraj P wrote:
> Thanks for the suggestions. We didnt have --mlockall parameter option in
> the rte_eal_init().
> we have just tried the option and our application says an *unrecognized
> option*.
> Lets us check further on this and let you know.
>
> Thanks,
> Kamaraj
>
No, that's not an EAL option, that's a testpmd option. However, that's
not really what i was asking.
If you have a custom application, and that application called mlockall()
(with appropriate flags) before EAL init, that would make all pages
pinned, present and future. That means, if you mmap() anonymous memory
(like EAL init does), it will take a long time because all of that
memory will be pinned (and since it's 4K pages because at that point,
we're not using hugepages yet, that will indeed take a long time).
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-02-19 15:28 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 [this message]
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=e88a771a-c7aa-9fe4-3934-091e18607e9f@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).