From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Need help with reducing VIRT memory
Date: Sun, 5 May 2024 12:35:51 +0300 [thread overview]
Message-ID: <20240505123551.6569236a@sovereign> (raw)
In-Reply-To: <CH3PR01MB8470EE23E69304BB80CFC1968F1D2@CH3PR01MB8470.prod.exchangelabs.com>
2024-05-05 03:25 (UTC+0000), Lombardo, Ed:
> 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?
DPDK has a general aim to convert options from compile-time to run-time.
However, these options would be considered in the last place if ever,
because high VIRT consumption has never been considered harmful before.
If you provide a detailed description of your use case
and explain how and why this interferes with your application needs,
the community can consider this rationale.
Technically, these options are easy to be made dynamic.
prev parent reply other threads:[~2024-05-05 9:35 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
2024-05-05 9:35 ` Dmitry Kozlyuk [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=20240505123551.6569236a@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=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).