DPDK usage discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: users <users@dpdk.org>
Subject: Re: DPDK 22.11.2 requires too much VIRT memory, how to reduce
Date: Sun, 5 Nov 2023 21:22:50 +0300	[thread overview]
Message-ID: <CAEYuUWDsPoTZXxv9SHdLbwDio7e36P__+j=ZGoL0=VzxAJG2WQ@mail.gmail.com> (raw)
In-Reply-To: <PH0PR01MB67301F1FBFD731EE7A48AD288FABA@PH0PR01MB6730.prod.exchangelabs.com>

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]

Hi Ed,

DPDK indeed reserves a large amount of virtual address space at startup.
This does not prevent DPDK from running on low-memory systems, since this
reservation does not consume physical memory. So the large figure in VIRT
is not an issue. Hugepages are mapped on demand. Each mapped hugepage
consunes a file descriptor. If you use 2MB hugepages, the number of open
files can exhaust the limit easily. If you don't want to increase it,
please see:
https://doc.dpdk.org/guides/prog_guide/env_abstraction_layer.html#segment-file-descriptors

>

[-- Attachment #2: Type: text/html, Size: 1040 bytes --]

  reply	other threads:[~2023-11-05 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05 16:00 Lombardo, Ed
2023-11-05 18:22 ` Dmitry Kozlyuk [this message]
2023-11-08 17:48   ` Lombardo, Ed
2023-11-08 18:12     ` Dmitry Kozlyuk
2023-11-08 22:26       ` Lombardo, Ed
2023-11-08 23:05         ` Dmitry Kozlyuk
2023-11-10  0:16           ` Lombardo, Ed
2023-11-10  9:31             ` Dmitry Kozlyuk
2023-11-10  9:37               ` Dmitry Kozlyuk
2024-03-14  2:51                 ` Lombardo, Ed

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='CAEYuUWDsPoTZXxv9SHdLbwDio7e36P__+j=ZGoL0=VzxAJG2WQ@mail.gmail.com' \
    --to=dmitry.kozliuk@gmail.com \
    --cc=Ed.Lombardo@netscout.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).