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: Fri, 10 Nov 2023 12:31:33 +0300 [thread overview]
Message-ID: <20231110123133.2adbd2cc@sovereign> (raw)
In-Reply-To: <PH0PR01MB6730BD9ACA0534A2BBBB2E5B8FAEA@PH0PR01MB6730.prod.exchangelabs.com>
Hi Ed,
2023-11-10 00:16 (UTC+0000), Lombardo, Ed:
> 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.
Right.
By default, DPDK can use up to 64 GB of hugepage memory,
so it reserves 64 GB of VIRT (but does not map most of it),
RES should be low until the app actually allocates something.
In legacy mode, DPDK maps all available hugepage memory at startup,
in your case 16 GB, VIRT and RES should be close.
> So I therefore had to increase the VM memory from 16 GB to 24 GB (instead
> of 80 GB without this setting).
I don't understand why you have to do that.
Possible VIRT is not limited by available RAM.
DPDK should be able to reserve 64 GB of VIRT on a machine with 16 GB of RAM,
it will just be unable to map more than 16 GB (obviously).
> 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 9:31 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
2023-11-10 9:31 ` Dmitry Kozlyuk [this message]
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=20231110123133.2adbd2cc@sovereign \
--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).