DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Need help with reducing VIRT memory
Date: Thu, 2 May 2024 19:05:13 +0000	[thread overview]
Message-ID: <CH3PR01MB8470BC421DA4DCE9E7840D978F182@CH3PR01MB8470.prod.exchangelabs.com> (raw)

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

Hi,
I have exhausted all my options and want to reach out to the dpdk developers for guidance.

My situation is as follows:
We were on DPDK 17.11.6 and upgraded to DPDK22.11.2 to support the Intel E810.  Also upgraded from CentOS7 to Oracle 91.
In DPDK 22.11.2 the VIRT memory has skyrocketed and causes major issues with our application that runs on 16 GB of memory (virtual appliances and low end remote appliances).

I have also tried DPDK 23.11 and 24.03 and I also see across the DPDK versions that the VIRT memory has increase by a factor of 5 over DPDK 17.11

Our application process shows VIRT memory is 7.6 GB with DPDK 17.11.6,
and with DPDK 22.11.2, 23.11.2 and 24.03 the VIRT memory is ~36.6GB

Our application minimum configuration needs to run with 16 GB memory when DPDK is enabled.  Our application uses memory locking and rlimit settings to get optimal performance.

I understand that DPDK memory design has changed since DPDK 18.xx.

We don't use hot-plug feature, encryption, security, telemetry, ipsec, or graph.
Currently we configure 2x1G hugepages and single socket.
I have tried to disable telemetry, cryptodev, etc in meson and only to find they can not be disabled, they are mandatory.

rte_eal_init() has argument "--legacy-mem", which brought down the VIRT memory to 36.6GB, but not enough.
Is there a developer guide to attack this problem in very low risk and timely fashion?

Thank you,
Ed

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

             reply	other threads:[~2024-05-02 19:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 19:05 Lombardo, Ed [this message]
2024-05-02 20:03 ` Dmitry Kozlyuk
2024-05-02 20:58   ` Lombardo, Ed
2024-05-03 14:48     ` Lombardo, Ed
2024-05-03 15:27       ` Bruce Richardson
2024-05-03 15:52         ` Bruce Richardson
2024-05-03 18:58           ` Morten Brørup
2024-05-03 20:07             ` Lombardo, Ed
2024-05-03 20:54       ` Dmitry Kozlyuk
2024-05-03 20:56         ` Dmitry Kozlyuk
2024-05-03 21:18           ` Lombardo, Ed
2024-05-04  6:51             ` Morten Brørup
2024-05-05  3:25           ` Lombardo, Ed
2024-05-05  9:35             ` 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=CH3PR01MB8470BC421DA4DCE9E7840D978F182@CH3PR01MB8470.prod.exchangelabs.com \
    --to=ed.lombardo@netscout.com \
    --cc=dev@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).