From: Szymon Szozda <szymonszozda@gmail.com>
To: users@dpdk.org
Subject: Dpdk allocates more memory, than available physically (hugepages)
Date: Wed, 8 Feb 2023 03:43:45 +0100 [thread overview]
Message-ID: <CAGsXdRRwpskhCoTYPz_kQ-DtTWgZBUnQ9MchkdtS49Yc87dGXw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
Hey,
I'm running dpdk on a machine with 64GB of RAM. It is configured, so 16GiB
(16 x 1GiB chunks) of hugepage memory is reserved on boot. I was expecting
dpdk to consume only those 16GiB, but it seems it gets more than 30GiB of
virtual memory ( I base it on memory VSZ output of top command ). The
machine is 1 NUMA, 1 NIC. I did some debugging and I do not see any logic
which limits the memory consumption, basically it seems that
eal_dynmem_memseg_lists_init() will allocate the same amount, no matter how
much RAM is physically available.
Is it expected? How to know that setup will not crash due to
insufficient memory available? How to limit those memory consumption.by
dpdk?
[-- Attachment #2: Type: text/html, Size: 757 bytes --]
next reply other threads:[~2023-02-13 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 2:43 Szymon Szozda [this message]
2023-02-13 15:46 ` Dmitry Kozlyuk
2023-02-13 17:17 ` Stephen Hemminger
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=CAGsXdRRwpskhCoTYPz_kQ-DtTWgZBUnQ9MchkdtS49Yc87dGXw@mail.gmail.com \
--to=szymonszozda@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).