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 7FF9744183; Fri, 7 Jun 2024 16:59:31 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 569E340272; Fri, 7 Jun 2024 16:59:31 +0200 (CEST) Received: from mail-oi1-f170.google.com (mail-oi1-f170.google.com [209.85.167.170]) by mails.dpdk.org (Postfix) with ESMTP id CC48940150 for ; Fri, 7 Jun 2024 16:59:29 +0200 (CEST) Received: by mail-oi1-f170.google.com with SMTP id 5614622812f47-3d21a80b8ceso20352b6e.3 for ; Fri, 07 Jun 2024 07:59:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1717772369; x=1718377169; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=HxlcWDiznE370QAKMRHDGq3XrcFYheZumPw0tE+9XsA=; b=HB0mgzsE/W+/AjB5PzjJEhOhwglXKwEkugCdiu5dJXJUoVa/HC0GAgpGJDA97SD2v7 jaM3Pqx6O9X+kSTlvyZZ5CE+iGKSzx74k0dMNPkdDdjszjwcFo99ZDgrdjWavIg96iml 1hEC0wgUmLd0mBkeh0kmgm4vAp9B3HAhl6aVg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717772369; x=1718377169; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=HxlcWDiznE370QAKMRHDGq3XrcFYheZumPw0tE+9XsA=; b=IpHezm9IWBUa+Ws5Z2DWmj7qgTpSsizkNE8E/FIcOB5gGa6LKEGz5YzpVTHNF9F0Yp mI/NBYb/IVgvXYEptnOFNJ3raJndiCdRcTUw/YaoPe9t3T/1vcXq1HPdxdBD7k1krlw5 tNIRYeGgIQ/OXgiSoO6+PpVGSEfqEk/MyUzaNfMZP2PRSWqtmge1VCYgGSp+5jZmwe4H /A4ZCdUH0xmjofprzWt3eh084DlbFxDvuRfsaJ4ZlD162VCw9Qa43qcMzUkRdt1JOdJ2 FwrLiwdMo18KwlRxSN8gMt7vhMftSIiZzjsWhiSCwAQ1uDHLKtkcZ/wmAmT86SjZjyAf 75ow== X-Gm-Message-State: AOJu0YxAxJR7T+4ifGPLbppMqmVkJL/tScCrw8XKZQ6yZqGwGnx5Vlwx slkuya2m8ZGfgT23mVj/QuRbJ+4S7q3r4WkjabPWvITYvw8+tOxLDjmurLyNDHU= X-Google-Smtp-Source: AGHT+IHQF4PwgguIASwvSVBa6LPLgdwtyghPS97kdi+jfet5Q4Plqee3c/O8VZh+3tDABU6w9V/OqA== X-Received: by 2002:a05:6870:7196:b0:250:6be3:3406 with SMTP id 586e51a60fabf-25464a0f070mr3063453fac.3.1717772368685; Fri, 07 Jun 2024 07:59:28 -0700 (PDT) Received: from localhost.unh.edu ([2606:4100:3880:1271:e2f8:4ec3:8bf3:864c]) by smtp.gmail.com with ESMTPSA id af79cd13be357-795330b2217sm174751485a.87.2024.06.07.07.59.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 07 Jun 2024 07:59:28 -0700 (PDT) From: Nicholas Pratte To: yoan.picchi@foss.arm.com, paul.szczepanek@arm.com, luca.vizzarro@arm.com, Honnappa.Nagarahalli@arm.com, jspewock@iol.unh.edu, bruce.richardson@intel.com, juraj.linkes@pantheon.tech, probb@iol.unh.edu Cc: dev@dpdk.org, Nicholas Pratte Subject: [PATCH v9 0/2] Methodology change for hugepage configuration Date: Fri, 7 Jun 2024 10:59:22 -0400 Message-ID: <20240607145925.27566-1-npratte@iol.unh.edu> X-Mailer: git-send-email 2.44.0 In-Reply-To: <20240430184533.29247-4-npratte@iol.unh.edu> References: <20240430184533.29247-4-npratte@iol.unh.edu> 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