[dpdk-dev] CONFIG_RTE_MAX_MEM_MB fails in DPDK18.05

Kamaraj P pkamaraj at gmail.com
Wed Feb 19 16:02:56 CET 2020


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

On Wed, Feb 19, 2020 at 7:53 PM Burakov, Anatoly <anatoly.burakov at intel.com>
wrote:

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


More information about the dev mailing list