DPDK usage discussions
 help / color / mirror / Atom feed
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: Wed, 8 Nov 2023 22:26:11 +0000	[thread overview]
Message-ID: <PH0PR01MB67302322AE1F6236E6C1DE218FA8A@PH0PR01MB6730.prod.exchangelabs.com> (raw)
In-Reply-To: <CAEYuUWCMHc4RyBKziEpDZryZuczQEzWW25AbOj71gnwkTcX2ZQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1078 bytes --]

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?

Thanks,
Ed

From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Sent: Wednesday, November 8, 2023 1:12 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.
My suggestions to use 1G hugepages and/or --single-file-segments were to counter "Too many open files" error, which you should observe no longer. "Out of memory" is a new error. What are the failing mmap() call arguments? For example, if it uses fixed addresses, it may clash with the area reserved by DPDK (also affected by --base-virtaddr). DPDK 23.11 should consume less RES memory at startup since it doesn't map it all but on demand. Does --legacy-mem option (which mimics the old babevior) affect the crash?

[-- Attachment #1.2: Type: text/html, Size: 4086 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 25080 bytes --]

  reply	other threads:[~2023-11-08 22:26 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 [this message]
2023-11-08 23:05         ` Dmitry Kozlyuk
2023-11-10  0:16           ` Lombardo, Ed
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=PH0PR01MB67302322AE1F6236E6C1DE218FA8A@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).