[dpdk-dev] CONFIG_RTE_MAX_MEM_MB fails in DPDK18.05

[Kamaraj P]

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.

Thanks,
Kamaraj
On Wed, Feb 19, 2020 at 8:58 PM Burakov, Anatoly <anatoly.burakov at intel.com>
wrote:

> 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
>