From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: users <users@dpdk.org>
Subject: RE: DPDK 22.11.2 requires too much VIRT memory, how to reduce
Date: Fri, 10 Nov 2023 00:16:54 +0000 [thread overview]
Message-ID: <PH0PR01MB6730BD9ACA0534A2BBBB2E5B8FAEA@PH0PR01MB6730.prod.exchangelabs.com> (raw)
In-Reply-To: <20231109020550.365e80bc@sovereign>
Hi Dmitry,
I finally finished testing all the options and found the VIRT value can be reduced from 66 GB to 16 GB with --legacy-mem setting in EAL init argument. So I therefore had to increase the VM memory from 16 GB to 24 GB (instead of 80 GB without this setting).
I wonder what do we give up with this setting?
All the other settings I tried and combinations of these had no impact (socket-limit=2048, single-file-segments, no-shconf, and no-telemetry) on VIRT memory.
Thanks,
Ed
-----Original Message-----
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Sent: Wednesday, November 8, 2023 6:06 PM
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
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.
2023-11-08 22:26 (UTC+0000), Lombardo, Ed:
> Hi Dmitry,
> I went to the dpdk.org and I don’t see DPDK 23.11,
>
> [cid:image001.png@01DA1268.AA1AC1F0]
>
> Do you have a pre-release version?
Sorry for the typo, I meant v22.11.2 that you're testing.
next prev parent reply other threads:[~2023-11-10 0:17 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
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 [this message]
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=PH0PR01MB6730BD9ACA0534A2BBBB2E5B8FAEA@PH0PR01MB6730.prod.exchangelabs.com \
--to=ed.lombardo@netscout.com \
--cc=dmitry.kozliuk@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).