From: Kamaraj P <pkamaraj@gmail.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.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 21:50:04 +0530 [thread overview]
Message-ID: <CAG8PAaowDOvWkeA0FUbUHz4UB85afhwnT7Wca0Asq4Q2YDeE-g@mail.gmail.com> (raw)
In-Reply-To: <0792d8b5-b0fd-15c8-f0ce-99a113c4c603@intel.com>
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.
Please see the screenshot below for reference:
ubuntu@client-server:~/dpdk/dpdk-stable/app/test-pmd/build/app$ sudo
./testpmd -l 0-3 -n 4 --log-level eal,8 -- -i --portmask=0x1 --nb-cores=2
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 0 on socket 0
EAL: Detected lcore 2 as core 0 on socket 0
EAL: Detected lcore 3 as core 0 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
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: DPAA Bus not present. Skipping.
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 1048576
EAL: Detected memory type: socket_id:0 hugepage_sz:2097152
EAL: Creating 4 segment lists: n_segs:8192 socket_id:0 hugepage_sz:2097152
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x10002e000 (size = 0x61000)
EAL: Memseg list allocated: 0x800kB at socket 0
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x100200000 (size = 0x400000000)
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x500200000 (size = 0x61000)
EAL: Memseg list allocated: 0x800kB at socket 0
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x500400000 (size = 0x400000000)
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x900400000 (size = 0x61000)
EAL: Memseg list allocated: 0x800kB at socket 0
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x900600000 (size = 0x400000000)
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0xd00600000 (size = 0x61000)
EAL: Memseg list allocated: 0x800kB at socket 0
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0xd00800000 (size = 0x400000000)
EAL: TSC frequency is ~2094950 KHz
EAL: Master lcore 0 is ready (tid=7f6507906c00;cpuset=[0])
EAL: lcore 1 is ready (tid=7f6505727700;cpuset=[1])
EAL: lcore 2 is ready (tid=7f6504f26700;cpuset=[2])
EAL: lcore 3 is ready (tid=7f6504725700;cpuset=[3])
EAL: Trying to obtain current memory policy.
EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: Restoring previous memory policy: 0
EAL: request: mp_malloc_sync
EAL: Heap on socket 0 was expanded by 2MB
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 15ad:7b0 net_vmxnet3
EAL: Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:0b:00.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 15ad:7b0 net_vmxnet3
EAL: Not managed by a supported kernel driver, skipped
EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)
testpmd: No probed ethernet devices
EAL: Trying to obtain current memory policy.
EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: Restoring previous memory policy: 0
EAL: request: mp_malloc_sync
EAL: Heap on socket 0 was expanded by 138MB
Interactive-mode selected
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=2176,
socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
EAL: Trying to obtain current memory policy.
EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: Restoring previous memory policy: 0
EAL: request: mp_malloc_sync
EAL: Heap on socket 0 was expanded by 4MB
EAL: Trying to obtain current memory policy.
EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: alloc_seg(): mmap() failed: Cannot allocate memory
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x110200000 (size = 0x200000)
EAL: attempted to allocate 194 segments, but only 56 were allocated
EAL: Restoring previous memory policy: 0
EAL: Trying to obtain current memory policy.
EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: alloc_seg(): mmap() failed: Cannot allocate memory
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x110200000 (size = 0x200000)
EAL: attempted to allocate 195 segments, but only 56 were allocated
EAL: Restoring previous memory policy: 0
EAL: request: mp_malloc_sync
EAL: Heap on socket 0 was shrunk by 4MB
EAL: Error - exiting with code: 1
Cause: Creation of mbuf pool for socket 0 failed: Cannot allocate memory
Thanks,
Kamaraj
On Wed, Feb 19, 2020 at 9:30 PM Burakov, Anatoly <anatoly.burakov@intel.com>
wrote:
> 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
>
next prev parent reply other threads:[~2020-02-19 16:20 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 [this message]
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=CAG8PAaowDOvWkeA0FUbUHz4UB85afhwnT7Wca0Asq4Q2YDeE-g@mail.gmail.com \
--to=pkamaraj@gmail.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=kamp@cisco.com \
--cc=ktraynor@redhat.com \
--cc=mtang2@cisco.com \
--cc=npenumar@cisco.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).