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 98F8FA0524;
	Thu, 30 Jan 2020 08:48:18 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id F31331BFF6;
	Thu, 30 Jan 2020 08:48:17 +0100 (CET)
Received: from mail-pg1-f181.google.com (mail-pg1-f181.google.com
 [209.85.215.181]) by dpdk.org (Postfix) with ESMTP id 50DD41BFE6
 for <dev@dpdk.org>; Thu, 30 Jan 2020 08:48:16 +0100 (CET)
Received: by mail-pg1-f181.google.com with SMTP id 6so1231196pgk.0
 for <dev@dpdk.org>; Wed, 29 Jan 2020 23:48:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=IMWG6Gx53xgyF7oEAeB5ECKjPX2pxpXr9tEbdgNHm04=;
 b=bKlB3ieqVQ+Jw8X9/ce8eThF1suGoagJsB1ZFng/spx7V3mjj/Zt4COYXGyb/acn4g
 mZdnxhiHl2KNKgPMX1ZBOWaiofQF7jkN0EyBbvjc1AbhNFPG+WLHSolHqFLrLJZERgVp
 7sp651mQrQo8RS7oxXGelMRCkdiWnJYyBWzcSD+FCDlaR0tq6zYtRq0X8V4Ol4+qlLBk
 syJeoqBPnKS8aNvBdAS48iveXG+iHDjA1XTeJVqkQkjzqmwckw76KXNErHHkeObprmZ4
 JG1ahLWEUUzgmPlZJpCz/h/ejhZKD5lLJkBfXOhbcmQOCxBO5B/DyM+VeJafEZOcGHbU
 hiSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=IMWG6Gx53xgyF7oEAeB5ECKjPX2pxpXr9tEbdgNHm04=;
 b=eVb8e7Kal5+J4DUagdf254fkmdApbtd0vElHI4jsIStL65PKTcZiY+AFY/GWa1SKj5
 Lhdp83hfV66fjlbrCP7LhdLYKV2+rhBndVA/jAJoJyHH17RdgMJNCbN/UuOBN5wxoilS
 DXTb8S2ZFw/n8cd0VYhYxJhUBL9ZvmWkV7qysFjYuI8zIbJhiiP3+Oqou5+B98tJe9LB
 POAfOiqolgzA7TeoZkHC/KSn38n4NR1vBxdPbBiUa/xppGJzey/QWXtTA7TYuZXbjxPk
 MZAcVWPTR0umBTs4o+ehEuBW9IOwAc14qlpXMX7Bu59Kbu6GgAiyfhUHXVqas2Cqt31g
 vEPA==
X-Gm-Message-State: APjAAAWfI41PeEAGNkZ9+jDqo32EkXij/ENIFE0c3HRK8I9Xxl++M5bb
 1j+Zq2KzZRM1O5HyPH161N3Rvtk9UgmuJGZVh4BTAA==
X-Google-Smtp-Source: APXvYqzWfKO28sVMvQf5VsSFfUzvr1rpLPy+gZl6lV5pjVYF8z+a3rtCGaJsw6zeQr2pqv6QpBTGPomB0uTtTI5S9/Q=
X-Received: by 2002:a65:4685:: with SMTP id h5mr3503936pgr.203.1580370495026; 
 Wed, 29 Jan 2020 23:48:15 -0800 (PST)
MIME-Version: 1.0
From: siddarth rai <siddsr@gmail.com>
Date: Thu, 30 Jan 2020 13:18:05 +0530
Message-ID: <CAGxAMwD6Wtfi=C2Txwjfk0zhFvRzeqBu7mFfE8ayh=EJi2aU-A@mail.gmail.com>
To: dev@dpdk.org
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] Big spike in DPDK VSZ
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>

Hi,

I have been using DPDK 19.08 and I notice the process VSZ is huge.

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

Is there anyway to disable allocation of such huge VSZ in DPDK ?
This is resulting in huge core files and I suspect that the problem will
compound on multi-NUMA machines.

Please help

Regards,
Siddarth