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 0FCC9432BD; Mon, 6 Nov 2023 22:05:20 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7B7A140E01; Mon, 6 Nov 2023 22:05:19 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id E8C48402BA for ; Mon, 6 Nov 2023 22:05:18 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 644DA5C02A1; Mon, 6 Nov 2023 16:05:18 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 06 Nov 2023 16:05:18 -0500 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=fm3; t= 1699304718; x=1699391118; bh=8CmQ2hX0y0EInibJ5vzaz3qF+bbvvgya+Vm 3mSFSssM=; b=JRShUeOCnE7QRRmkHXnDIwKjZaosiTkEB+DgCLqpPoYqBmp5P2H FSAqv9Jy7lichJTtSlT7RJjTIdD1RkSHksKeJky9MfrHrYHoHVIu2l5jZL7Fw2Yj vDA5B+m4z1QRg+/3st4dgd2yxK6pUD0bA0VHeAHdNidn8gSTH2Y1jTbIPy037+hR swhpQR/698baUqxYbyVjQMcNChNEBCM9yZIt5izvZpkRNX9fx50sKv5oxkpifQnZ LDcbM3Q/hFKbAyMvigP7WJsX4VgP9pUAa1i+MrYVrmb9RJm+AUnNFydkUk7GYOnl anBqKeI6fBghv97p2i7jVBhqrzDgFmiWf6w== 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=fm3; t= 1699304718; x=1699391118; bh=8CmQ2hX0y0EInibJ5vzaz3qF+bbvvgya+Vm 3mSFSssM=; b=X/KOBVfZHL3DhMFTUQVaInRi3q20bLtt4PPfZykVrkavywvJltY NIDrx8VTwg61OXkh00fizCtY+e/Rrsc1lkqpKuRrklcijCcHtiFmnbBfYb91fQyf nUHyS6PHQk1zvjSuocSQnZAHx2v6PylguBUCa0B7BcAMgbqMw1gUrB8z9sFEt8zA wzkPM8Utakm6SMNozKROX4eTizv4ZPbHRQYZWupDOY8JWZxMmL07Z1Xyz15hTZt8 0U6ZeYrxJCYaRibgBbOLD+rIg4cbLnl8Tsze499yLdcZ8Li4oM2/YRL/9IPjvzun nHYioWWo3/EuEhpBk/IqKetnibhbPuIivxA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedruddugedgudegvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttdejnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnheplefggfelvdeigfekffdtkeehieduudeugfekudegueekteek heejveeguddutefhnecuffhomhgrihhnpeguphgukhdrohhrghdpnhgrmhhprhguuddvrd hprhhougenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhm pehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 6 Nov 2023 16:05:16 -0500 (EST) From: Thomas Monjalon To: Kevin Traynor , "Tummala, Sivaprasad" , David Marchand , Ferruh Yigit , bruce.richardson@intel.com, konstantin.v.ananyev@yandex.ru, Morten =?ISO-8859-1?Q?Br=F8rup?= , maxime.coquelin@redhat.com, Aaron Conole Cc: dev@dpdk.org Subject: Re: [PATCH] config/x86: config support for AMD EPYC processors Date: Mon, 06 Nov 2023 22:05:15 +0100 Message-ID: <15039672.JCcGWNJJiE@thomas> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9EF51@smartserver.smartshare.dk> References: <20230925151027.558546-1-sivaprasad.tummala@amd.com> <98CBD80474FA8B44BF855DF32C47DC35E9EF51@smartserver.smartshare.dk> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" 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 17/10/2023 12:27, Morten Br=C3=B8rup: > > >> From: Tummala, Sivaprasad > > >>> From: David Marchand > > >>> On Mon, Sep 25, 2023 at 5:11=E2=80=AFPM Sivaprasad Tummala > > >>>> From: Sivaprasad Tummala > > >>>> > > >>>> By default, max lcores are limited to 128 for x86 platforms. > > >>>> On AMD EPYC processors, this limit needs to be increased to > > leverage > > >>>> all the cores. > > >>>> > > >>>> The patch adjusts the limit specifically for native compilation on > > >>>> AMD EPYC CPUs. > > >>>> > > >>>> Signed-off-by: Sivaprasad Tummala > > >>> > > >>> This patch is a revamp of > > >>> > > >> > > http://inbox.dpdk.org/dev/BY5PR12MB3681C3FC6676BC03F0B42CCC96789@BY5PR > > >>> 12MB3681.namprd12.prod.outlook.com/ > > >>> for which a discussion at techboard is supposed to have taken place. > > >>> But I didn't find a trace of it. > > >>> > > >>> One option that had been discussed in the previous thread was to > > >>> increase the max number of cores for x86. > > >>> I am unclear if this option has been properly evaluated/debatted. >=20 > Here are the minutes from the previous techboard discussions: > [1]: http://inbox.dpdk.org/dev/YZ43U36bFWHYClAi@platinum/ > [2]: http://inbox.dpdk.org/dev/20211202112506.68acaa1a@hermes.local/ >=20 > AFAIK, there has been no progress with dynamic max_lcores, so I guess the= techboard's conclusion still stands: >=20 > There is no identified use-case where a single application requires more = than 128 lcores. If a case a use-case exists for a single application that = uses more than 128 lcores, the TB is ok to update the default config value. >=20 > > >>> > > >>> Can the topic be brought again at techboard? > > >> > > >> Hi David, > > >> > > >> The patch is intended to detect AMD platforms and enable all CPU > > cores by default > > >> on native builds. >=20 > This is done on native ARM builds, so why not on native X86 builds too? >=20 > > >> > > >> As an optimization for memory footprint, users can override this by > > specifying "- > > >> Dmax_lcores" option based on DPDK lcores required for their usecases. > > >> > > >> Sure, will request to add this topic for discussion at techboard. This is the summary of the techboard meeting: (see https://mails.dpdk.org/archives/dev/2023-October/279672.html) =2D There is some asks for more than 128 worker cores =2D Discussion about generally increasing the default max core count and trade-offs with memory consumption but this is longer term issue =2D Acceptance for the direction of this patch in the short term =2D Details of whether it should be for EPYC only or x86 to be figured out on mailing list So now let's figure out the details please. Suggestions?