From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D220F42BF1; Mon, 5 Jun 2023 18:51:03 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 572614021F; Mon, 5 Jun 2023 18:51:03 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id 15EB64003C for ; Mon, 5 Jun 2023 18:51:02 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 8E4D85C00D8; Mon, 5 Jun 2023 12:51:01 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 05 Jun 2023 12:51:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1685983861; x=1686070261; bh=Xl1IhPZ2lKrqsrWeQfbsk0VFoE9Lc2LRNKN J3H31zFg=; b=PhJFWrbefn3rlgoSPxavdtPXottVtloCdH0c4KkFXPQo53+++Cn bz0EjuloIaaKvzTcenKlLH9MJy+TlxW5vi4Y1uiWCKFlR1vsHCl1t1cMRIqmTj74 XlNMP2n2kvYeNIzv7t7OprlesfuuUrvPC/yQhlB3bCAu1QcNf5t1OM51LJKfSs9p Oz4q+anYTLEwNoyjMhkzjTQTflVGFfYgeZcwFp+bTZYRlM3xIAZP2ffJeAPKFzbE UChDqswnovPtIoRcLd4O4AvHRfjtY4sa73uA6Kx7nMhApGU4F/YV5D/SbtqMD2s4 PSLOKi862SZ4qj0DkdFUwPFUMRIAcjsaqRQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1685983861; x=1686070261; bh=Xl1IhPZ2lKrqsrWeQfbsk0VFoE9Lc2LRNKN J3H31zFg=; b=XRd235wt0nKSkim1fE3RPVhyCpZo0p6Lu296JCf9qJ6hL36aQbj s8hukHVwPgnEjjkLzU80bUEzrBk7bW2ZVI0HGVtw7FVsByp+8or10NT9t6fyNcSq vs6MKDSUghVg3asp/cFUQaHB7tZTmo/4nqevSamEIWLThaCO3pcIE6mHAeACNmvn GsGpyd+Uvvy5PGuFRuH3LRBuFCWHhf8aXpCqueY4V6qufiY2Tu/mAZi++Cnr7aja nuW6x4CsFAJtAXu4X+2O7ElsfIBblqJAuAU4IkeNjrDcAuw0I0Nx9tOImdHkH4wm AopxL3x5xLL2GIStslAYCUaYH7d3VByIlsg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeelledguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttddunecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnhepfefhjeeluedvvedtuddtuedtvefhieejtefhffeujefhtedu udevtdektdeikeffnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 5 Jun 2023 12:50:59 -0400 (EDT) From: Thomas Monjalon To: Ophir Munk Cc: dev@dpdk.org, Bruce Richardson , Devendra Singh Rawat , Alok Prasad , Maayan Kashani , Matan Azrad , Lior Margalit , David Marchand , Anatoly Burakov Subject: Re: [PATCH V8] lib: set/get max memzone segments Date: Mon, 05 Jun 2023 18:50:58 +0200 Message-ID: <11471862.RiKt1P0BV1@thomas> In-Reply-To: <20230605105028.496197-1-ophirmu@nvidia.com> References: <20230605085200.492223-1-ophirmu@nvidia.com> <20230605105028.496197-1-ophirmu@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 05/06/2023 12:50, Ophir Munk: > Currently, the max memzones count constat (RTE_MAX_MEMZONE) is used to > decide how many memzones a DPDK application can have. This value could > technically be changed by manually editing `rte_config.h` before > compilation, but if DPDK is already compiled, that option is not useful. > There are certain use cases that would benefit from making this value > configurable. >=20 > This commit addresses the issue by adding a new API to set the max > number of memzones before EAL initialization (while using the old > constant as default value), as well as an API to get current maximum > number of memzones. >=20 > Signed-off-by: Ophir Munk > Acked-by: Morten Br=F8rup > Acked-by: Alok Prasad Did minor changes in comments and function sorting. Applied, thanks.