From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: Need help with reducing VIRT memory
Date: Sun, 5 May 2024 03:25:21 +0000 [thread overview]
Message-ID: <CH3PR01MB8470EE23E69304BB80CFC1968F1D2@CH3PR01MB8470.prod.exchangelabs.com> (raw)
In-Reply-To: <20240503235632.27ea47f4@sovereign>
Hi Dmitry,
I tried your settings tonight and the application VIRT memory is now 7.9G and is in the ball park, you are amazing.
#define RTE_MAX_MEMSEG_LISTS 2
#define RTE_MAX_MEMSEG_PER_LIST 1024
#define RTE_MAX_MEM_MB_PER_LIST 2048
#define RTE_MAX_MEMSEG_PER_TYPE 1024
#define RTE_MAX_MEM_MB_PER_TYPE 2048
There is no possibility to change these settings at run-time? Maybe I asking too much? Maybe would be something DPDK developers can consider?
Thanks,
Ed
-----Original Message-----
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Sent: Friday, May 3, 2024 4:57 PM
To: Lombardo, Ed <Ed.Lombardo@netscout.com>
Cc: dev@dpdk.org
Subject: Re: Need help with reducing VIRT memory
External Email: This message originated outside of NETSCOUT. Do not click links or open attachments unless you recognize the sender and know the content is safe.
2024-05-03 23:54 (UTC+0300), Dmitry Kozlyuk:
> #define RTE_MAX_MEM_MB_PER_LIST 2024 // see item 4 below
Typo: 2048
next prev parent reply other threads:[~2024-05-05 3:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 19:05 Lombardo, Ed
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 [this message]
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=CH3PR01MB8470EE23E69304BB80CFC1968F1D2@CH3PR01MB8470.prod.exchangelabs.com \
--to=ed.lombardo@netscout.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
/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).