From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id D3A54A0524;
	Thu, 30 Jan 2020 14:18:31 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id CED441BFFC;
	Thu, 30 Jan 2020 14:18:30 +0100 (CET)
Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178])
 by dpdk.org (Postfix) with ESMTP id 739D21BFFA
 for <dev@dpdk.org>; Thu, 30 Jan 2020 14:18:29 +0100 (CET)
Received: by inbox.dpdk.org (Postfix, from userid 33)
 id 5AD1CA0525; Thu, 30 Jan 2020 14:18:29 +0100 (CET)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Thu, 30 Jan 2020 13:18:28 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: core
X-Bugzilla-Version: 19.11
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: major
X-Bugzilla-Who: siddsr@gmail.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 target_milestone
Message-ID: <bug-386-3@http.bugs.dpdk.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-dev] [Bug 386] Big spike in DPDK process VSZ since release
	18.05.1
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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

            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-memor=
y'
option it goes up to 188G.

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


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

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