All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 386] Big spike in DPDK process VSZ since release 18.05.1
Date: Thu, 30 Jan 2020 13:18:28 +0000	[thread overview]
Message-ID: <bug-386-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=386

            Bug ID: 386
           Summary: Big spike in DPDK process VSZ since release 18.05.1
           Product: DPDK
           Version: 19.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: siddsr@gmail.com
  Target Milestone: ---

Hello,

I am currently using DPDK 19.11. I notice the process virtual size is huge.

I tried running the test PMD. It takes 64G VSZ and if I use the '--in-memory'
option it goes up to 188G.

Is there anyway to disable allocation of such huge VSZ in DPDK ? 


Also I found that version 18.02.2 doesn't have the problem, but 18.05.1 and
further releases have it.

Would really appreciate if someone can help, if there is a patch to get over
this issue in the DPDK code ?
This is becoming a huge practical issue as huge core files are getting
generated. On multi NUMA setup, the VSZ goes above 400G and I can't get core
files to debug crashes in my app.

Regards,
Siddarth

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-01-30 13:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-386-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.