DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: Szymon Szozda <szymonszozda@gmail.com>, users@dpdk.org
Subject: Re: Dpdk allocates more memory, than available physically (hugepages)
Date: Mon, 13 Feb 2023 09:17:39 -0800	[thread overview]
Message-ID: <20230213091739.7f663fee@hermes.local> (raw)
In-Reply-To: <20230213184614.3039b1af@sovereign>

On Mon, 13 Feb 2023 18:46:14 +0300
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote:

> 2023-02-08 03:43 (UTC+0100), Szymon Szozda:
> > 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?  
> 
> Hi,
> 
> DPDK always reserves a large chunk of virtual address space,
> but this costs almost nothing and does not need to be limited.
> Then DPDK maps and unmaps actual pages to those addresses as needed.
> DPDK does not crash if it runs out of hugepages reserved in the system
> but merely returns NULL from its allocation API (rte_malloc).
> Real memory consumption can be limited with --socket-limit EAL option.
> See also --socket-mem and -m to reserve hugepages at DPDK startup.

Hugepages are mainly used for buffers and shared driver resources.
The normal text and data are not in hugepages (unless you figure
out how to use hugelbfs). Memory consumption limiting is best
done with cgroups. But most applications die if they can't get the
memory they need.  You can see where memory is used with /proc/XXX/maps

      reply	other threads:[~2023-02-13 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08  2:43 Szymon Szozda
2023-02-13 15:46 ` Dmitry Kozlyuk
2023-02-13 17:17   ` Stephen Hemminger [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=20230213091739.7f663fee@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=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).