From: Lucas <lucascrijns@gmail.com>
To: users@dpdk.org
Subject: Increase DPDK's virtual memory to more than 512 GiB
Date: Wed, 19 Feb 2025 15:22:46 +0100 [thread overview]
Message-ID: <CADTTPn8Cgu3ShDWWGdd9whQQAmiFH9x9MaweZ4DR3XHdcww6Eg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
Hello,
I am creating an application where I want to cache packets in a ring for a
certain duration. To do so at high speed (100 Gb/s) for tens of seconds, I
would like to create a mempool with a size bigger than 500 GiB.
I know that in rte_config.h, we have this excerpt:
```
#define RTE_MAX_MEMSEG_LISTS 128
...
#define RTE_MAX_MEM_MB_PER_LIST 32768
```
4'194'304 MiB of addressable memory, which is more than enough. However,
there is a virtual memory limit on DPDK processes on x86_64, which appears
to be 512 GiB.
at https://doc.dpdk.org/guides/prog_guide/env_abstraction_layer.html it is
listed that RTE_MAX_MEM_MB controls that.
In the meson.build file in the config directory, we have:
```
if dpdk_conf.get('RTE_ARCH_64')
dpdk_conf.set('RTE_MAX_MEM_MB', 524288)
else # for 32-bit we need smaller reserved memory areas
dpdk_conf.set('RTE_MAX_MEM_MB', 2048)
endif
```
Changing this value does not seem to change the amount of virtual memory
that DPDK allocates. It appears that no headers or C-files actually
reference this value.
What would I need to change to allow more virtual memory than 512 GiB and
be able to allocate a mempool with a size bigger than that?
Thank you in advance for any pointers!
Kind regards,
Lucas Crijns
[-- Attachment #2: Type: text/html, Size: 1634 bytes --]
next reply other threads:[~2025-02-19 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 14:22 Lucas [this message]
2025-02-19 15:03 ` Stephen Hemminger
2025-02-19 22:28 ` Dmitry Kozlyuk
[not found] ` <CADTTPn-zDTotOsCsnkuEQiRDdEfuLGVDo1hmuXetgGLd+TTP6Q@mail.gmail.com>
2025-02-20 11:21 ` Dmitry Kozlyuk
2025-02-20 14:19 ` Lucas
2025-02-20 14:55 ` Dmitry Kozlyuk
2025-03-03 14:52 ` Lucas
2025-03-03 22:05 ` Dmitry Kozlyuk
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=CADTTPn8Cgu3ShDWWGdd9whQQAmiFH9x9MaweZ4DR3XHdcww6Eg@mail.gmail.com \
--to=lucascrijns@gmail.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).