From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 66705293B5F for ; Sun, 28 Jun 2026 19:38:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782675536; cv=none; b=BomQju+o5D+CfZ9H7yfNJqHeA4LtJjlAC3sS1EPJvjx8jI4uBxD6OPgg5djuTyX4Jc12hBEgymiwcNwvs8Ebcc6EyLZ0M3hS/lDghf4EDb7Pw6RYzwsf4qveKr689JllmcfDYLhzin9u3RMBMrnlHOTArDAv4ZGRV/TExDuuvWQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782675536; c=relaxed/simple; bh=IelR8p1cNPgiyfOVbPd42cayQAksNpDL42jkTZjSqiU=; h=Date:From:To:Cc:Subject:Message-Id:In-Reply-To:References: Mime-Version:Content-Type; b=TzwA/rZcwo/e/PEnEHHCvZCXh5HQwVzjR7QSRPoOpqP+WZeDKNWTnn6OA+hufMIIHJNpHqF2SjNRS5oQGKUBOcG2W8ELeiBSK3u1FfXTHhJoyJKgO1Nf2RIm5lHpcrqCe+u9HoV1s5F9KhSKgmRFB6EcgTj3kuBKxXU8KbU3aZw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=Z05HUhdD; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="Z05HUhdD" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 97A081F000E9; Sun, 28 Jun 2026 19:38:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=korg; t=1782675534; bh=CuTzCncB1dSE/gH/AIAOqd09rcNMzjDsf7JAoAwCjrk=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=Z05HUhdDYeLWuSpWdVqthRJCkd2YEuESciZULtAVFpQQQVWrW5D/AUn/d8OkI0gob QXfvNiQagEL4yjesc0PXEwstDXkfJL9SY9ULCpX3sksUC/gDebY8MXxxfQihGeBf8I GQiI142Yka5uXrMWjukYJC/ZkHhrR8UYxwkfFyws= Date: Sun, 28 Jun 2026 12:38:54 -0700 From: Andrew Morton To: Sourav Panda Cc: muchun.song@linux.dev, osalvador@suse.de, david@kernel.org, surenb@google.com, fvdl@google.com, gthelen@google.com, rientjes@google.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] mm/hugetlb_cma: support percentage-based hugetlb_cma reservation Message-Id: <20260628123854.862fd5d430894fe451b34323@linux-foundation.org> In-Reply-To: <20260628190155.3655895-1-souravpanda@google.com> References: <20260628190155.3655895-1-souravpanda@google.com> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 28 Jun 2026 19:01:55 +0000 Sourav Panda wrote: > Currently, hugetlb_cma reservation only supports absolute sizes (e.g., > hugetlb_cma=2G or hugetlb_cma=0:1G,1:1G). This can be restrictive in > heterogeneous environments or when deploying common kernel command lines > across machines with different memory capacities. > > Add support for percentage-based hugetlb_cma reservation (e.g., > hugetlb_cma=20% or hugetlb_cma=0:20%,1:10%). > > The percentage is calculated against the total memory (for global > settings) or against the node-specific memory (for node-specific > settings) using memblock APIs during early boot. Thanks, I'll queue this for testing and additional review. There are a couple of pr_infos in this code, to give people an understanding of how the kernel has sized these things. Would it make sense to enhance those, to help our operator to understand/confirm what effect the chosen percentage configuration had? > Signed-off-by: Sourav Panda > Reported-by: kernel test robot > Closes: https://lore.kernel.org/oe-kbuild-all/202606262023.IKUrn01I-lkp@intel.com/ Robot found issues in the v1 patch. This development-time info isn't something which we (at least, I) normally include in the permanent kernel record.