From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6E8FDA04FA; Sun, 2 Feb 2020 10:22:44 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A205A1BFEB; Sun, 2 Feb 2020 10:22:43 +0100 (CET) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) by dpdk.org (Postfix) with ESMTP id 6C34B4C90 for ; Sun, 2 Feb 2020 10:22:42 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1580635361; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=7L0TJu3VjzRpHkYnsuTrLSOHNW9TFOI/CwyicPSTioc=; b=OU54e3a4wuTheVDyT47+4JZUJ681P5co3gQSoHagGY1iNEQsSodBzEao6PRWBTDvOJItou QvjqG6u/43rHQKz09UkGqTmmda2gEDtjrAfklRWksAAEv8GjAdJkJH6BS4nXNAhzLRWCWc C8S4GrhNou1yu/xrSsqmK5pk+l9m2YE= Received: from mail-vk1-f199.google.com (mail-vk1-f199.google.com [209.85.221.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-310-phPKwIgYObu9NYWrYV9kew-1; Sun, 02 Feb 2020 04:22:36 -0500 Received: by mail-vk1-f199.google.com with SMTP id k16so3766089vko.11 for ; Sun, 02 Feb 2020 01:22:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uRYeZdQBtrgsTjFdzv4E0afBB2burQdK6KyoWuLuzts=; b=D5f+koeNJRpXmhLUhHZAs5X8+QpG03rKwvWTf2PgiCuc9nSCoV4qdT+dgZMIkVX5Cx EdeyIOSK31o/uHYiQb8Mxn7L5/G/EAFJTgP20rfogaFed/UqhKmMOFSuo1UbqwF2yq0f VJoxOOodbkTYLEoOi24/WEiYvQ4wx1lILKDHytcg3sXqxOjw2mEV6Y8Vuw/I7pNVn98h VNa6DXjpWNBBeBl+8U/STyHhZ2lgyaiaLtwmolex268yHGAlcYMcXbw0PSLPgbisCCI4 Mtcv+iiBv/+mcN3DQv+TUSSjylmYUrTM51dJH5esmVADxX31gXOPkNHKkbNHhd4rB3gr 3sZw== X-Gm-Message-State: APjAAAX47Lb3goOPHx0uWoxnLMPE58VylCXwOAFqCcpjFLzqeFzYsGnS MRYywQh3YA2Pj5/liTddWSTXJ8RO60buQxTFrVuCiN6oi3ydYuqhts73h/f2v8WG+eTSYzDRzdc Nv8VZQVxXjscgBgDGiBQ= X-Received: by 2002:ab0:488b:: with SMTP id x11mr10968530uac.86.1580635355997; Sun, 02 Feb 2020 01:22:35 -0800 (PST) X-Google-Smtp-Source: APXvYqyRwXX7j5ZrhVHG1eBBHZfZpQJsa/7app1rqZz8+bspKb6DC/hfxX7f7mM9oGhLQmE7bJ/Ar+ZLK5PWn8+TX8w= X-Received: by 2002:ab0:488b:: with SMTP id x11mr10968517uac.86.1580635355681; Sun, 02 Feb 2020 01:22:35 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Sun, 2 Feb 2020 10:22:24 +0100 Message-ID: To: siddarth rai , "Burakov, Anatoly" Cc: dev , julien.meunier@nokia.com X-MC-Unique: phPKwIgYObu9NYWrYV9kew-1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Jan 30, 2020 at 8:48 AM siddarth rai wrote: > > 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. For this particular issue, it might be interesting to look at madvise stuff= : MADV_DONTDUMP (since Linux 3.4) Exclude from a core dump those pages in the range specified by addr and length. This is useful in applications that have large areas of memory that are known not to be useful in a core dump. The effect of MADV_DONTDUMP takes precedence over the bit mask that is set via the /proc/PID/coredump_filter file (see core(5)). (FreeBSD seems to have a MADV_NOCORE flag too). --=20 David Marchand