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 A2C3A4326D; Thu, 2 Nov 2023 11:04:31 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7699040282; Thu, 2 Nov 2023 11:04:31 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 1091040262 for ; Thu, 2 Nov 2023 11:04:30 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id A33825C009B; Thu, 2 Nov 2023 06:04:27 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Thu, 02 Nov 2023 06:04:27 -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:message-id:mime-version:reply-to :sender:subject:subject:to:to; s=fm3; t=1698919467; x= 1699005867; bh=PL/BW4FMuqFHbFI/7Mng+RAdixKwMoroIbmAgls1Jtw=; b=l ZVtMk0A0Y+67Ty8pgP1mjSRgUCIXmL88A7E0sBdqpJQwNwasVYEzn/xINleSgUlr Gg/BsP27fhbPyEf/NvwCdUbDBnSj/7VeS23I5+8F5+RzvSDVKFNE23QmPprgqz1k HNxwX0VJwnV9UFZj2MLUZ0tjrOXVXe2HQDbsnhmz6eZegjFdd1aKdFCJEyop7uaw tndJ53pm90iJGl6hxwGNBlQ5KN4Wk/jQKef4EmQyTiYj/gOpEfA7yBUMZxU4/0DO zvS1AOnR5kOvx/IYE5FPLGD8WeaDQ8Js5YqiEvRmuOS2ivIXhH0+lLAK1Tajx0Vv aM78tO+2G8Uml2WRyYytg== 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:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1698919467; x=1699005867; bh=P L/BW4FMuqFHbFI/7Mng+RAdixKwMoroIbmAgls1Jtw=; b=iS5RhjwflP24MwrM5 jhgg3Lx9y2RTFdfSsSZG98mGDbbd94Vi1L+O0FfQDWiIQwnGft42HCNfhuSWfe4o usfJWd1zoD449Bvfbbw44nUGeqtkEJdN2dTUogSUNbY5KBAe2HK7W8H9aZ/+1wGy TkfYVHAruCl0cw8rBO96fAX+pJcGdKejQ9YFY59HaUEJfqNbcBsqitHxHhSPSw9Q +aa/Jc7JfQptQTeLwwZc7v//L+iReLeP6Ca0P2wScSZ/9tJz+O/CbyYOmBL7ZHkJ DgGAP2RJwF6EgbPnUFnIAzS3aljgjy+5/oHa3IgAiyo55yHCE6yPO037toNaWCgv JrbcA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedruddtiedgudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkfgggfgtsehtufertd dttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehm ohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepvefhieeugedvffefhfevvd ejiefhheefhffhvedvuedtteethffhfeeileegheevnecuffhomhgrihhnpehgihhthhhu sgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 2 Nov 2023 06:04:25 -0400 (EDT) From: Thomas Monjalon To: anatoly.burakov@intel.com Cc: david.marchand@redhat.com, bruce.richardson@intel.com, dev@dpdk.org, Kefu Chai , avi@scylladb.com Subject: configuration of memseg lists number Date: Thu, 02 Nov 2023 11:04:24 +0100 Message-ID: <3585796.R56niFO833@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 Hello, While looking at Seastar, I see it uses this patch on top of DPDK: build: add meson options of max_memseg_lists RTE_MAX_MEMSEG_LISTS = 128 is not enough for high-memory machines, in our case, we need to increase it to 8192. so add an option so user can override it. https://github.com/scylladb/dpdk/commit/cafaa3cf457584de I think we could allow to configure this at runtime, as we did already for RTE_MAX_MEMZONE: we've added rte_memzone_max_set() / rte_memzone_max_get(). Opinions, comments, volunteers?