* [dpdk-dev] [Bug 386] Big spike in DPDK process VSZ since release 18.05.1
@ 2020-01-30 13:18 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2020-01-30 13:18 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-01-30 13:18 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-30 13:18 [dpdk-dev] [Bug 386] Big spike in DPDK process VSZ since release 18.05.1 bugzilla
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).