Dpdk allocates more memory, than available physically (hugepages)
Szymon Szozda
szymonszozda at gmail.com
Wed Feb 8 03:43:45 CET 2023
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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/users/attachments/20230208/142c74f0/attachment.htm>
More information about the users
mailing list