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 E0F3843E14; Sat, 6 Apr 2024 10:47:53 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9968E402C0; Sat, 6 Apr 2024 10:47:52 +0200 (CEST) Received: from dkmailrelay1.smartsharesystems.com (smartserver.smartsharesystems.com [77.243.40.215]) by mails.dpdk.org (Postfix) with ESMTP id 971AD4028C for ; Sat, 6 Apr 2024 10:47:51 +0200 (CEST) Received: from smartserver.smartsharesystems.com (smartserver.smartsharesys.local [192.168.4.10]) by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id 607EB21276; Sat, 6 Apr 2024 10:47:51 +0200 (CEST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [PATCH] dts: Change hugepage runtime config to 2MB Exclusively Date: Sat, 6 Apr 2024 10:47:48 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F36D@smartserver.smartshare.dk> In-Reply-To: <20240404153106.19047-1-npratte@iol.unh.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PATCH] dts: Change hugepage runtime config to 2MB Exclusively Thread-Index: AdqGpSQIJULy9ogNQT+A2lMKAmGahgBWRtqQ References: <20240404153106.19047-1-npratte@iol.unh.edu> From: =?iso-8859-1?Q?Morten_Br=F8rup?= To: "Nicholas Pratte" , , , , , , , Cc: , "Jeremy Spewock" 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 > From: Nicholas Pratte [mailto:npratte@iol.unh.edu] > Sent: Thursday, 4 April 2024 17.31 >=20 > The previous implementation configures and allocates hugepage sizes > based on a system default. This can lead to two problems: = overallocation > of > hugepages (which may crash the remote host), and configuration of > hugepage > sizes that are not recommended during runtime. This new implementation > allows only 2MB hugepage allocation during runtime; any other unique > hugepage size must be configured by the end-user for initializing DTS. >=20 > If the amount of 2MB hugepages requested exceeds the amount of 2MB > hugepages already configured on the system, then the system will = remount > hugepages to cover the difference. If the amount of hugepages = requested > is > either less than or equal to the amount already configured on the > system, > then nothing is done. >=20 > Bugzilla ID: 1370 > Signed-off-by: Nicholas Pratte > Reviewed-by: Jeremy Spewock > --- This change seems very CPU specific. E.g. in x86 32-bit mode, the hugepage size is 4 MB, not 2 MB. I don't know the recommended hugepage size on other architectures.