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 6418AA0524; Thu, 30 Jan 2020 11:48:01 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0829D1BFE6; Thu, 30 Jan 2020 11:48:00 +0100 (CET) Received: from mail-pg1-f170.google.com (mail-pg1-f170.google.com [209.85.215.170]) by dpdk.org (Postfix) with ESMTP id 3E8181BFE5 for ; Thu, 30 Jan 2020 11:47:58 +0100 (CET) Received: by mail-pg1-f170.google.com with SMTP id s64so1431293pgb.9 for ; Thu, 30 Jan 2020 02:47:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lzJ2qmcHDiqePzgH42nOTZ0xUjxPMt9x2CRkzEfEOp0=; b=oweKQzTZyHEqdgWiP0xa2u/EjXfmRTRvaIjQIWAXsavq/Uvaw+FuN81isA7h57KwUw NKF8YojPTi/ppLs2m3bZCAojvW/83mcIxXMNRuIT9M1z3WDbxCaESkAqSCN6zIuZBsJb RM1FaF1dYSczyQ1fb4XlZCfG5+BVukWgVY2zVd2/wWw2HjqtwDlBOnMlCGQlbVt2m9JN /cfXCzJ8rAavj+8DzVo26XeQ/P/cuQ6B10LmqnQvxeC7yQaS809IAXnI0jnXOZf5LJ5h lxs4z0Uhk2qtPqKt+XNJA+Ale1QdAWZo3PTaGEdstPrD8232UIq9wJhT8HczGMkcpKmn bJpQ== 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=lzJ2qmcHDiqePzgH42nOTZ0xUjxPMt9x2CRkzEfEOp0=; b=HMahbgVsHvn8vAhlrYiZ3KMnW+hxWKa7+smpY/cjP1HgcGtZx/IqwtTmynolHoGdC9 gvV/zcqpNRTzFzgy8hBSdFjr+OD5C0AMkvReON2NWA8T4zbAHRspTuH0yxtnDPpcOLjm kh4JcopFW7OgLMZRJoWTkBqexr2krCag742mxDzY7zthSuHnQVcj+ai3/5I2VkjOm6a+ HklCY6PQhLifBV/KHSP3/Vs4aORZXJ54xPR7ZnoSAuFrtUTPRjDinmKwrL0u39PL7+cb IK6oql+APkgsJJ8J/qTvKRfk+VEy/fAOuBw2cMz3/Qe2GXRV4vwj4ssmj6ebpZJ94HnW DN3Q== X-Gm-Message-State: APjAAAUoldmp24Xe2mJfd4v9875BxkToEx0MECzGTwlNqOf7HLYeAdvt +Cw4U9zIeRagQDfqUyVLdC7gPibjbuYyji8Te70= X-Google-Smtp-Source: APXvYqxjnSWtqUzRlcit4L08domPAnI4HRqpCMFNC7JqL42WysHb5ll/pF4EH/a3SpizX+a15bxCb9ZwJJSmONh+3RE= X-Received: by 2002:aa7:8193:: with SMTP id g19mr4452129pfi.172.1580381277143; Thu, 30 Jan 2020 02:47:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: siddarth rai Date: Thu, 30 Jan 2020 16:17:47 +0530 Message-ID: To: David Marchand Cc: "Burakov, Anatoly" , dev Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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" Hi, I did some further experiments and found out that version 18.02.2 doesn't have the problem, but the 18.05.1 release has 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 for me as on multi NUMA setup, the VSZ goes above 400G and I can't get core files to debug crashes in my app. Regards, Siddarth Regards, Siddarth On Thu, Jan 30, 2020 at 2:21 PM David Marchand wrote: > On Thu, Jan 30, 2020 at 8:48 AM siddarth rai wrote: > > 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 ? > > *Disclaimer* I don't know the arcanes of the mem subsystem. > > I suppose this is due to the memory allocator in dpdk that reserves > unused virtual space (for memory hotplug + multiprocess). > > If this is the case, maybe we could do something to enhance the > situation for applications that won't care about multiprocess. > Like inform dpdk that the application won't use multiprocess and skip > those reservations. > > Or another idea would be to limit those reservations to what is passed > via --socket-limit. > > Anatoly? > > > > -- > David Marchand > >