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 8689B43FCC; Tue, 7 May 2024 19:44:48 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 691EC43460; Tue, 7 May 2024 19:44:48 +0200 (CEST) Received: from mail-qv1-f53.google.com (mail-qv1-f53.google.com [209.85.219.53]) by mails.dpdk.org (Postfix) with ESMTP id 92F5C402DF for ; Tue, 7 May 2024 19:44:47 +0200 (CEST) Received: by mail-qv1-f53.google.com with SMTP id 6a1803df08f44-6a0e9ebfc84so4690036d6.0 for ; Tue, 07 May 2024 10:44:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1715103887; x=1715708687; 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=PEosgovwpCzEWBzbGzfaahlDTKIYXedTUTkpimZty1g=; b=Hhh1Zrigp6J6kRwLOlZqqfDVSFRQfkVCveb6uuJMy0n8xtpGNYCEyPwO2tA3NaorOj qgO2i/ytS2Dl5RSaX721tID5MAxsrrFAY8cT7NsP5b0PG77fWKXo0b3NnJraAQH5dkPQ DUMdLTK+qn01Z9e656uz4QcQZXEAqqm/dud+Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715103887; x=1715708687; 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=PEosgovwpCzEWBzbGzfaahlDTKIYXedTUTkpimZty1g=; b=DT0xMh/3VDZkI+U1XGvydiNKRAHgIui3unc5DPDiNSgoS9xlFGn/hkFboHayNX+Rsu 3S+WW4KY4PAmSzuV653KPUO+yillr31d6gF5c4h8OULxpYDBtDxqSX+XujbGIM+CxClg X3tKs+aqikXQvuySau4AKaNUcY60ZdnM3mptcQ9al8GaCq/zckKAVspr8uJW5Zl4hPe3 cj316HUmvQd2uU8uzwWwduNeuJT/7tyTzisVIq4e6WMOAoF7wi0OZ4hIToFlZ1Lj7Nai X/wiMnVBo9kZklp5YrC6y0hv2PfONeq8vC6FOeE+sg0ljlR27Wt58zhtoUy4YT5f+UK5 XRUw== X-Gm-Message-State: AOJu0YzH1EPwr/DJFdiVaHOjLnOy6BzzR/wVS0u4cJL9UPuMUMSot0y6 tmFr1WlIR3cpM/dqVBSXrZ9h8HCmyYfk3IeD3aa4cfxcg5D51eMDlCXVet/nf24= X-Google-Smtp-Source: AGHT+IH71QYz+otXmZTkiO5ykIM/mdPRGxrzzEMO8CDjRC59QeHu+7cJLpml4hQK6WOJZwgZorQjCQ== X-Received: by 2002:a05:622a:449:b0:437:cc82:9c00 with SMTP id d75a77b69052e-43dbec14395mr5220641cf.0.1715103886892; Tue, 07 May 2024 10:44:46 -0700 (PDT) Received: from localhost.unh.edu ([2606:4100:3880:1271:e2f8:4ec3:8bf3:864c]) by smtp.gmail.com with ESMTPSA id bp20-20020a05622a1b9400b00434a165d45asm6621623qtb.38.2024.05.07.10.44.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 May 2024 10:44:46 -0700 (PDT) From: Nicholas Pratte To: probb@iol.unh.edu, bruce.richardson@intel.com, Honnappa.Nagarahalli@arm.com, juraj.linkes@pantheon.tech, thomas@monjalon.net, jspewock@iol.unh.edu, yoan.picchi@foss.arm.com, mb@smartsharesystems.com, wathsala.vithanage@arm.com, paul.szczepanek@arm.com Cc: dev@dpdk.org, Nicholas Pratte Subject: [PATCH v6 0/2] Methodology change for hugepage configuration Date: Tue, 7 May 2024 13:44:28 -0400 Message-ID: <20240507174430.29403-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 | 6 ++++- 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 | 7 ++++- 8 files changed, 45 insertions(+), 32 deletions(-) -- 2.44.0