DPDK patches and discussions
 help / color / mirror / Atom feed
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 16:00:28 +0000	[thread overview]
Message-ID: <0792d8b5-b0fd-15c8-f0ce-99a113c4c603@intel.com> (raw)
In-Reply-To: <CAG8PAaoy6gTAskB+Zp=AjQ0hetqb=0502y1Kg0G1q7zyqquxQQ@mail.gmail.com>

On 19-Feb-20 3:42 PM, Kamaraj P wrote:
> Hi Anatoly,
> Thanks for the suggestions. Yeah we have just changed in our application 
> to invoke mlockall() before rte_eal_init(). Looks like it does not help 
> either.
> 
>       if (mlockall(MCL_CURRENT | MCL_FUTURE)) {
>           printf("Failed mlockall !! ******\n");
>       }
>      ret = rte_eal_init(argc, args);
> 
> Looks like still observing the struck issue when allocating virtual pages.
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 1 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: open shared lib /usr/lib64/librte_pmd_ixgbe.so.2.1
> EAL: open shared lib /usr/lib64/librte_pmd_e1000.so.1.1
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Module /sys/module/vfio_pci not found! error 2 (No such file or 
> directory)
> EAL: VFIO PCI modules not loaded
> EAL: Probing VFIO support...
> EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)
> EAL: VFIO modules not loaded, skipping VFIO support...
> EAL: Ask a virtual area of 0x2e000 bytes
> EAL: Virtual area found at 0x100000000 (size = 0x2e000)
> EAL: Setting up physically contiguous memory...
> EAL: Setting maximum number of open files to 4096
> EAL: Detected memory type: socket_id:0 hugepage_sz:2097152
> EAL: Creating 32 segment lists: n_segs:1024 socket_id:0 hugepage_sz:2097152
> EAL: Ask a virtual area of 0xd000 bytes
> EAL: Virtual area found at 0x10002e000 (size = 0xd000)
> EAL: Memseg list allocated: 0x800kB at socket 0
> EAL: Ask a virtual area of 0x80000000 bytes
> 
> Could you please suggest if there is any other option which we need to 
> try it out.
Does this only happen with your application, or does it happen with DPDK 
example applications or test/testpmd apps?

-- 
Thanks,
Anatoly

  reply	other threads:[~2020-02-19 16:00 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 [this message]
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=0792d8b5-b0fd-15c8-f0ce-99a113c4c603@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).