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 D82EDA0524; Thu, 30 Jan 2020 09:51:35 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 721801BFE6; Thu, 30 Jan 2020 09:51:34 +0100 (CET) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) by dpdk.org (Postfix) with ESMTP id 861011BFE5 for ; Thu, 30 Jan 2020 09:51:32 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1580374291; 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=xR6B032Q4fQVVp5wFhB87YHxnJkY4JJa8we2NFNjlsY=; b=JrcMAasS/6998AIN5cpWvxa2UPgWexsagLCIGKloTk4qt6X4OWz6K5dI1DwNvVXeB3OpTl TWYrqRsNIzDs8+TMlQSeUMZuOo9tJbYvbRE6EML5BcPmIqYEFMCtHrb6T2RqaYcgq+hC7X pZ7WLfAjxuEGe5LWcm0uUv+4gjBRa/A= Received: from mail-vk1-f200.google.com (mail-vk1-f200.google.com [209.85.221.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-211-dwC-ILCwMNWxH5mBGvqFDg-1; Thu, 30 Jan 2020 03:51:29 -0500 Received: by mail-vk1-f200.google.com with SMTP id i123so969312vkg.8 for ; Thu, 30 Jan 2020 00:51:29 -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=xR6B032Q4fQVVp5wFhB87YHxnJkY4JJa8we2NFNjlsY=; b=ebXQKFyh1Oh2/ru0vMBn+R9oqPoaCA9WHl0eew/T+ni1m1/5ZZvf6dHY2Df7cYfunk DwdSAfZIxPLWPmk2BgdKrHHJtw0asmDlcqRifYS4iG/yJKa0tHOg1hP+02NTUZsMJE9c HPfeqCVGTIjOerVDUADoyQvckhzgTJo8bNmMN4kRfVwmLM/p2XzT+h5HoVh465GM4Qpn RGM5dz/ms1uJvOGSY/ppj796d2G0pVMNHnTl0DdZ7aojYY84lhZJE2QEAmKh2K+Ai3jv 5xTbIIhQgaBB0WtERuEa//PdFgXP9W7CcU6ya8BesaSBRKWWEHkDLGK6FglqYIP1F4k5 8GJQ== X-Gm-Message-State: APjAAAXuwr7TZqJCgrWSBCU1z4P/OdJYKySJH7jkfeP+06dzbWj961Jd gExkI6zYz1rXdqOYsgaZfDjoYi+h3a3iqScZv8dZ3udqClwQMPtklUXDSUsV3n7WwpkOgdk8PP9 aePM+rFBIubvhn82FaAg= X-Received: by 2002:a67:905:: with SMTP id 5mr2471997vsj.105.1580374289424; Thu, 30 Jan 2020 00:51:29 -0800 (PST) X-Google-Smtp-Source: APXvYqym2gpA8tO94wrP3OPYOsC+53o7MCvshRR/nj/kxIZFcfWeojo+NAH3D+/yO1kY9oHUbojMCqfmm1Y/JeL6llM= X-Received: by 2002:a67:905:: with SMTP id 5mr2471987vsj.105.1580374289162; Thu, 30 Jan 2020 00:51:29 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Thu, 30 Jan 2020 09:51:18 +0100 Message-ID: To: siddarth rai , "Burakov, Anatoly" Cc: dev X-MC-Unique: dwC-ILCwMNWxH5mBGvqFDg-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: > 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