From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 042DC239 for ; Tue, 24 Jul 2018 12:23:51 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1F58821B81; Tue, 24 Jul 2018 06:23:51 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 24 Jul 2018 06:23:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=990PJ3cSjLms60PTbcH9hG68jY rk1eQ94IL6S6VjSGk=; b=KZ/x0fn972EXLxMAsQy1k15EEXT3f/xHa5n9h8BhXm nSjk5Q/a8YcCyHxjYUfupXiyAe/AaFPSa9vFoBtyghUUP4NZCK8hG2bEryKht3Ry vcnc8gw6NPF0+gb5cEVXcInmrwhIxCANks+TWVNKW7TwK8z5MpmCxayLgINqh+i0 0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=990PJ3 cSjLms60PTbcH9hG68jYrk1eQ94IL6S6VjSGk=; b=PI6vOLRhiXO0fyo+/IsJHr 4awtywhZ1UDqFTOp0/+2zofhiBZHCJ0nawpky7MddBZr0d6Sfvb2TMOrWA1MY12U TxaXRqw1AD7RWwENLIP7ZQeTXzQatAx4Rh3AwmfU5oh9czSxRZClv+mUwd3QbmS1 tu6VETXVbCxhaHidYhztHY+fiZ6t/AVF2rAzGslkjFPVS3VrRQMBbxErRSSh9tVX lNHY+yrqAJZxGz6ZO6vSdgmaOrH05EVH9yzDGaSbf3glL4mQah7eTRBAKOHRLbRM iwFRpJw/afA7FDpAwX+OZPgGhg43uRMzv8nEXI8mNLLkd4E8Xn9qp+qOKp1CzhoA == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 3EEEDE4BB5; Tue, 24 Jul 2018 06:23:50 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: dev@dpdk.org, Ravi1.Kumar@amd.com Date: Tue, 24 Jul 2018 12:23:45 +0200 Message-ID: <7333019.QUcIvQh70r@xps> In-Reply-To: <40cf48703f5fae8af8c31dcc8a1a1ecb0b151d27.1532426170.git.anatoly.burakov@intel.com> References: <40cf48703f5fae8af8c31dcc8a1a1ecb0b151d27.1532426170.git.anatoly.burakov@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] config: reduce memory requirements for DPDK 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: , X-List-Received-Date: Tue, 24 Jul 2018 10:23:52 -0000 24/07/2018 12:03, Anatoly Burakov: > It has been reported that current memory limitations do not work > well on an 8-socket machines in default configuration when big > page sizes are used [1]. > > Fix it by reducing memory amount reserved by DPDK by default to > 32G per page size per NUMA node. This translates to allowing us > to reserve 32G per page size per NUMA node on 8 nodes with 2 > page sizes. > > [1] https://mails.dpdk.org/archives/dev/2018-July/108071.html > > Signed-off-by: Anatoly Burakov > --- > > Notes: > We could have increased CONFIG_RTE_MAX_MEM_MB but this would've > brought other potential problems due to increased memory > preallocation, and secondary process initialization is flaky > enough as it is. I am willing to bet that 32G per page size is > more than enough for the majority of use cases, and any > application with bigger requirements could adjust config options > itself. [...] > -CONFIG_RTE_MAX_MEMSEG_PER_TYPE=32768 > -CONFIG_RTE_MAX_MEM_MB_PER_TYPE=131072 > +CONFIG_RTE_MAX_MEMSEG_PER_TYPE=16384 > +CONFIG_RTE_MAX_MEM_MB_PER_TYPE=32768 Ideally, it should be a run-time option.