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 41445424C1; Mon, 10 Jun 2024 17:21:19 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D7018402A9; Mon, 10 Jun 2024 17:21:18 +0200 (CEST) Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com [209.85.160.181]) by mails.dpdk.org (Postfix) with ESMTP id 31E4740294 for ; Mon, 10 Jun 2024 17:21:17 +0200 (CEST) Received: by mail-qt1-f181.google.com with SMTP id d75a77b69052e-440f93a8ffeso139021cf.3 for ; Mon, 10 Jun 2024 08:21:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1718032876; x=1718637676; darn=dpdk.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=HxlcWDiznE370QAKMRHDGq3XrcFYheZumPw0tE+9XsA=; b=Bm8cuSjGU8tZJUCTKOL8sl3uBKmDkkMfqi57Ry+a0/Qi2Td8W8BUyl5H/1BdlZ/YHa Wa9CknIdv9isMjCzcR5Tkykqzngphhwsa27Bfkk5JJ09lKbgQMfIB1Btt7wmroC0VT8Q tomTah3Xn2+Ur3SMJ69Lpfgf4FpmZxIxs4jEo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718032876; x=1718637676; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HxlcWDiznE370QAKMRHDGq3XrcFYheZumPw0tE+9XsA=; b=nWT5vNT/9+FFRcYamq89XADv2DY1REZtp2yddzzgGMaD6QVmHiTWX95mKtcGUbDO25 KoguyPm+PFwtxDD9HqC8OKMpS3hCRPoxefyhtFchcnmZoFt713YfRrjoqe4v6p/5DqtE STz7SsHHYXpmDkxHkFuzmfSIcKTSTN8+NXtoVeTIdA1PpnT5TTNNJPDq75TTMTyDmYvy KljPFMWBQb5lUKK59tNQMS5nMop4QhAXeHI8AWd0XFqUeMsva5xnFDX+jqbYUni1y6Fm GlsTbE3lokH6+3Yt0mt0pIQNB8eGU1G6XaRqypKREqo9xL2GWWqhc9UK3PBaoKrOA9vb 9fyg== X-Gm-Message-State: AOJu0YzFkbQj3/FxPsnquf2D9BLi6g53WCuxa/2hSKtJjbMMv49PtnLt DlY+CwF1Rka9CmK6RltxpqZNVfoTW7cv6dGFGFPt2fcC8/oj/8tcip61s+lfGpQ= X-Google-Smtp-Source: AGHT+IGbBhRGZ8ob14lLMzaqgFluOmTKVI9SR8M+tKrANg9AT45XHy+IMlF7J5Wtn7km5LTWNGUJtA== X-Received: by 2002:a05:622a:50:b0:441:1de:8ab0 with SMTP id d75a77b69052e-44101de918fmr23165751cf.2.1718032876226; Mon, 10 Jun 2024 08:21:16 -0700 (PDT) Received: from localhost.unh.edu ([2606:4100:3880:1271:e2f8:4ec3:8bf3:864c]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-441208c5072sm3070551cf.78.2024.06.10.08.21.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Jun 2024 08:21:15 -0700 (PDT) From: Nicholas Pratte To: luca.vizzarro@arm.com, jspewock@iol.unh.edu, paul.szczepanek@arm.com, Honnappa.Nagarahalli@arm.com, yoan.picchi@foss.arm.com, juraj.linkes@pantheon.tech, probb@iol.unh.edu, bruce.richardson@intel.com Cc: dev@dpdk.org, Nicholas Pratte Subject: [PATCH v9 0/2] Methodology change for hugepage configuration Date: Mon, 10 Jun 2024 11:20:46 -0400 Message-ID: <20240610152048.23617-2-npratte@iol.unh.edu> X-Mailer: git-send-email 2.44.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 In order to prevent accidental misconfiguration of hugepages at runtime, the following changes are made to only allow for configuration of 2MB hugepages within the DTS config.yaml. In the previous implementation, a default hugepage size was selected via the size listed in /proc/meminfo. The problem with this implementation is that, assuming the end-user has made prior modifications to the system, /proc/meminfo may default to hugepage sizes that are not recommended to be configured at runtime (i.e. 1GB hugepages). This can lead to two problems: overallocation of hugepages (which may crash the remote host) configuration of hugepages sizes that are not recommended during runtime. In this new implementation, we stipulate that any runtime hugepage configuration size that is not 2MB is considered an outlier. If the end-user would like to configure either 1GB hugepages or any unique hugepage size outside of 2MB, then they should make these configurations either at startup (in the case of 1GB hugepages) or runtime outside of DTS configuration (if a user would like hugepages that are not 2MB). In either case, the expectation is that, if wish to use hugepage sizes that are not 2MB, you will make these changes outside and prior to the initialization of DTS. The end-user has two options: remove the option for hugepage configuration in the conf.yaml, or keep the option and specify the amount of 2MB hugepages desired. In the case of the former, then we assume that hugepages are already configured prior to DTS initialization. In the latter case, the user must define the amount of 2MB hugepages to be configured at runtime. 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 greater than or equal to the amount already configured on the system, then nothing is done. Nicholas Pratte (2): dts: Change hugepage runtime config to 2MB Exclusively dts: Change hugepage 'amount' to a different term doc/guides/tools/dts.rst | 14 ++++++---- dts/conf.yaml | 8 +++--- dts/framework/config/__init__.py | 8 +++--- dts/framework/config/conf_yaml_schema.json | 12 ++++----- dts/framework/config/types.py | 4 +-- dts/framework/testbed_model/linux_session.py | 28 ++++++++++---------- dts/framework/testbed_model/node.py | 4 ++- dts/framework/testbed_model/os_session.py | 9 ++++--- 8 files changed, 48 insertions(+), 39 deletions(-) -- 2.44.0