From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7AF01C433FE for ; Sun, 10 Oct 2021 20:55:20 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 11BC560F22 for ; Sun, 10 Oct 2021 20:55:20 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 11BC560F22 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 3DE9C900002; Sun, 10 Oct 2021 16:55:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 38EEF6B0072; Sun, 10 Oct 2021 16:55:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 2A59C900002; Sun, 10 Oct 2021 16:55:19 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0042.hostedemail.com [216.40.44.42]) by kanga.kvack.org (Postfix) with ESMTP id 16B426B006C for ; Sun, 10 Oct 2021 16:55:19 -0400 (EDT) Received: from smtpin09.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id B95FD2C698 for ; Sun, 10 Oct 2021 20:55:18 +0000 (UTC) X-FDA: 78681733116.09.1DD88D5 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf14.hostedemail.com (Postfix) with ESMTP id 404336005B90 for ; Sun, 10 Oct 2021 20:55:18 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id 00D0160F22; Sun, 10 Oct 2021 20:55:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1633899317; bh=VYCfwXiqKXGp+9DR4kGNpPumSvCR33w/NigEzc864Uc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=ce0Wp/bo+NqkOapQsnRUSupU2/wwmTEQw9dT3zM5utafLvqJYMZl4/j5dAE793RFK wY4cwrcgKbv+BwRRCKOwTbnenr3NqGQNkr9F+cZHphVvJTwh7eu9j5RXPOHb48+rND HJFNPxnJc8sJGdm6K0TFRYb6irR1wClntharx0i8= Date: Sun, 10 Oct 2021 13:55:07 -0700 From: Andrew Morton To: Baolin Wang Cc: mike.kravetz@oracle.com, mhocko@kernel.org, guro@fb.com, corbet@lwn.net, yaozhenguo1@gmail.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH] hugetlb: Support node specified when using cma for gigantic hugepages Message-Id: <20211010135507.f2d1c6bcaeecc82d6d025604@linux-foundation.org> In-Reply-To: <1633843448-966-1-git-send-email-baolin.wang@linux.alibaba.com> References: <1633843448-966-1-git-send-email-baolin.wang@linux.alibaba.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 404336005B90 X-Stat-Signature: obmg5do3rz1fao4ba4pz65rbk53q78uf Authentication-Results: imf14.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b="ce0Wp/bo"; dmarc=none; spf=pass (imf14.hostedemail.com: domain of akpm@linux-foundation.org designates 198.145.29.99 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org X-HE-Tag: 1633899318-422515 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Sun, 10 Oct 2021 13:24:08 +0800 Baolin Wang wrote: > Now the size of CMA area for gigantic hugepages runtime allocation is > balanced for all online nodes, but we also want to specify the size of > CMA per-node, or only one node in some cases, which are similar with Please describe in full detail why "we want to" do this. In other words, what is the benefit to our users? What are the use-cases, etc? > commit 86acc55c3d32 ("hugetlbfs: extend the definition of hugepages > parameter to support node allocation")[1]. > > Thus this patch adds node format for 'hugetlb_cma' parameter to support > specifying the size of CMA per-node. An example is as follows: > > hugetlb_cma=0:5G,2:5G > > which means allocating 5G size of CMA area on node 0 and node 2 > respectively. >