From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Robert Hable <Robert.Hable@spusu.at>
Cc: "users@dpdk.org" <users@dpdk.org>,
Tyler Retzlaff <roretzla@microsoft.com>,
"Dmitry Malloy (MESHCHANINOV)" <dmitrym@microsoft.com>
Subject: Re: Windows mbuf pool memory allocation
Date: Tue, 27 Sep 2022 19:01:56 +0300 [thread overview]
Message-ID: <20220927190156.31d59e0f@sovereign> (raw)
In-Reply-To: <PAXP190MB174152D30E8F2B32720EEE8DE1559@PAXP190MB1741.EURP190.PROD.OUTLOOK.COM>
Hi Robert,
2022-09-27 15:22 (UTC+0000), Robert Hable:
> Hello,
>
> I have a question about mbuf pool memory allocation. When I have my machine freshly started, it usually works flawless to run testpmd. But after a few days uptime sometimes the allocation of the mbuf pool fails. Currently I get the error "Not enough space".
> What could be the reason behind this that it works after a reboot, but not after a few days uptime?
> According to the windows taskmanager there is still 32.8 GB free memory, and only 30.3 GB is currently used.
Looks like RAM fragmentation.
If the system is out of contiguous hugepage spans, --iova-mode=va should help.
If the system cannot find contiguous RAM for a single 2MB hugepage,
there's not solution that I know of, there's no option to reserve hugepages
(or none that I know of---Dmitry, Tyler?)
>
> c:\Dev\Extern\dpdk\build\app>dpdk-testpmd.exe
> EAL: Detected CPU lcores: 20
> EAL: Detected NUMA nodes: 1
> EAL: Multi-process support is requested, but not available.
> EAL: Probe PCI driver: mlx5_pci (15b3:1015) device: 0000:01:00.0 (socket 0)
> mlx5_common: DevX read access NIC register=0X9055 failed errno=0 status=0 syndrome=0
> mlx5_net: mlx5_os_dev_shared_handler_install: is not supported
> mlx5_net: Rx CQE 128B compression is not supported.
> EAL: Probe PCI driver: mlx5_pci (15b3:1015) device: 0000:01:00.1 (socket 0)
> mlx5_common: DevX read access NIC register=0X9055 failed errno=0 status=0 syndrome=0
> mlx5_net: mlx5_os_dev_shared_handler_install: is not supported
> mlx5_net: Rx CQE 128B compression is not supported.
> testpmd: create a new mbuf pool <mb_pool_0>: n=299456, size=2176, socket=0
> testpmd: preferred mempool ops selected: ring_mp_mc
> EAL: Error - exiting with code: 1
> Cause: Creation of mbuf pool for socket 0 failed: Not enough space
--log-level=lib.eal:debug would show which allocation failed.
prev parent reply other threads:[~2022-09-27 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 15:22 Robert Hable
2022-09-27 16:01 ` Dmitry Kozlyuk [this message]
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=20220927190156.31d59e0f@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=Robert.Hable@spusu.at \
--cc=dmitrym@microsoft.com \
--cc=roretzla@microsoft.com \
--cc=users@dpdk.org \
/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).